Around 12 years ago I helped design and set up a 48-drive, 9U, ~120TB NAS in the Chenbro RM91250 chassis (still going strong! but plenty of drive failures along the way...). This looks like it's probably the 24-drive/4U entry in the same line (or similar). IIRC the fans were very noisy in their original hot-swappable mounts but replacing them with fixed (screw) mounts made a big difference. I can't tell from the picture if this has hot-swappable fans, though - I think I remember ours having purple plastic hardware.
There is no "Google Docs" format, though - you have no idea how Google is representing your data, or if there even is any single "blob" that is your file (and even if there is one on the server side, AFAIK you can't get it). I'm not very familiar with Notion, but it seems like it's probably the same way. That means there's no chance of "Google Docs" or "Notion" becoming a standardized format. At least with a proprietary standalone format you (or the community) has a chance at reverse engineering it.
My guess is that the output PDF is still valid, but that an embedded (subset) font has had its `ToUnicode` map stripped, so that there's no link between the character codes used in the text elements and the "actual" characters they represent (there are also other ways this corruption could happen, but dropping or mangling the `ToUnicode` map seems like a likely cause).
Yep, and in that case it's because those PDFs were often generated through really horrifying pipelines (e.g. TeX to DVI to PS to PDF). Under some workflows, the resulting document wouldn't even contain any characters, as far as PDF was concerned -- it'd just be a bunch of vectors.
I agree. If you look closely, you can see certain patterns repeating, they’re just not English letters. But it definitely looks like natural language, and not random binary dump.
Crappy bike infrastructure (e.g. sharrows, bike lanes that end and dump cyclists onto bad/dangerous roads) is a negative for everyone: cyclists, drivers, bike advocates,... better to save the money and build more limited but higher quality infrastructure.
I actually built this product out (for both Uber and Lyft) - SMS/MMS-based ride requests (MMS only for sending google maps PNGs to confirm pickup location). I was about to convert it from a personal project (I used it to get rides on both services for a few years) to a "real" one open to customers, etc and then ran into snags with both APIs at around the same time. Uber's API changed to potentially require a web flow to confirm surge pricing (IIRC - now it's scheduled to be disabled entirely very soon) and Lyft's API was basically shut off entirely (there's a way to apply but I was unable to make any progress even through internal contacts at Lyft). I'll try and keep an eye out for any changes...
I'm stunned by the fact they have a graph comparing two stock tickers by share price. Do they not realize that comparison is essentially meaningless (without market cap, etc)? If you look at YTD performance Copart is actually doing worse than the competitor they're comparing against...
You gotta understand, once you're not in the top 4 newspapers, it's people working for almost free just pooping out articles. Then G/O Media got Spanfeller from this exact crummy magazine, and now even their properties are suffering.
It's actually not too bad. You can run a pool of soffice processes, but unless you really care about the startup time, I'd suggest running individual processes per job, which you can run headless from the command line. For the most part libreoffice does well, although at some point you'll start to discover the quirks in their rendering...
I absolutely agree - Arabic is a beautiful language and a joy to learn, and it is particularly appealing for those who enjoy structure and regularity (e.g. CS and math folk!). Be forewarned, though - the significant differences between MSA (modern standard Arabic, the focus of most "Arabic" courses/material) and regional/national dialects (and the differences between those various dialects themselves) may make it a bit less practical than you'd hope (and a source of disappointment when you go to actually speak with people!).
It's basically an online version of Hans Wehr, the de facto standard dictionary for students of Arabic. You can search by root or by word and provides form I vowelling, masadir (infinitives), broken plurals, and other useful information organized by form. I know there exist other good dictionaries out there, but I never found one I quite liked as a reference as much as I enjoyed Hans Wehr. I hope someone else finds it useful! (I've been neglecting it a bit recently, so I apologize for any bugs and for the lack of an SSL cert).
You have no idea how long I’ve been waiting for something like this, without the time to implement it myself. All these years I’ve had to use http://ejtaal.net/mr/ but it’s just getting quite cumbersome.
Do you have any plans to open source the work you’ve done and allow contributions from the outside? I could easily see value in doing this for Lane’s Lexicon as well.
I'll try to answer my own question: I knew Wehr's dictionary was fairly old, but it may be old enough that it has entered public domain. There are still major publishers that publish the dictionary, but it may well be public domain.
For me one of the largest (if not THE largest) factor* in bike safety is route choice, and the main factor in that for me is density and speed of car traffic. As comfortable as I feel "vehicular" cycling (e.g. cutting across lanes to take a true left turn, taking the lane to avoid the "dooring zone" along parked cars), those are the moments when I am most exposed and at risk. Likewise the safest intersections are those that do not have cars passing through!
As an example, a colleague of mine commutes from near my house to our office, and we take very different routes - him along a major artery with (mostly) protected bike lanes, me along back streets with sharrows or no bike markings at all. Even in a protected line, he has to contend with fast and constant traffic alongside him, frequent intersections where he has no protection and is even harder to see (since he's popping out from behind a line of parked cars); the intersections are constantly in use and drivers turn and accelerate faster to make smaller windows in the faster traffic. My commute along back streets is leisurely; I can ride in the middle of the street without fear of getting doored or getting overtaken at speed unexpectedly, and intersections are calm. Of course the major artery is more direct (and so perhaps slightly faster), but it's also a major designated bike route and for that reason sees a lot of bike traffic even though I think it's less safe.
Of course in denser neighborhoods and cities it may be difficult to find "back streets" with minimal car traffic and which still get to where you're going. Still, I think that should be a goal of new bike infrastructure development - I'm happy to act like a car, make turns from the correct lane, stop at red lights, signal, etc., and I don't need a protected bike lane either - a normal road with light, slow car traffic is fine. A set of these which connects the major neighborhoods in a community (e.g. running parallel to arteries but not quite in the central areas) makes for a very nice bike experience (c.f. Berkeley's bike boulevards which is naturally my inspiration here!).
So, when this article mentions the requirement of protected bike lanes on all streets, while I think that's great and I love seeing bicycling given more consideration in urban planning, I also think that it seems a little coarse. Some roads don't need to have any bike traffic at all, some roads can be wonderful for biking without any modification at all, and some roads ought to be made better for biking but in more nuanced ways (primarily traffic easing - roundabouts, narrower roadways, removing through-access, etc - that discourages car traffic without impeding bike traffic). Of course if you want to build independent bike trails (or non-grade lanes, or other more significant changes) that's wonderful too!
Other important factors IMO:
Cyclist density - everyone should bike! Probably preaching to the choir here but there's safety in numbers, drivers get used to seeing cyclists and how they behave, and it makes it easier to advocate for better infrastructure. Also relevant on a micro-level for route choice
* Cycling experience/behavior - including "vehicular" maneuvers, general awareness of dangerous/risky situations and driver behavior
* Lights
