4,805 karma · joined January 14, 2009
It's not any worse than you'd have if you were starting from scratch with your own hardware, but Bryan Cantrill is firmly against magic block storage. His suggestion is that you rewrite your persistence layer to know about SDC or "deal with it".
It's not necessarily that bad since a lot of containers don't need state, but my personal axe is that I work with databases almost exclusively.
To that extent, I'm not sure that tossing out the idea of hosts is great yet.
Personally, I'm very much into Ratliff (or banner style) indentation and using two spaces for your indent. I know that 4 is the standard for a lot of people, but my feeling is that this is generally the result of people using VeryLongVariableNamesThatGoOnForever and blocks that go on for a many lines.
The more concise code becomes and the shorter your blocks get, I have found that it becomes much more annoying to have to skip your eye further. This gets especially silly if you have anything with deep nesting.
Ratliff style just makes it so so easy to tell where a block terminates though. I have basically no idea why it isn't wildly popular.
Probably because editors don't support it.
I dunno, just a thought, but do you get what I'm saying about recognition vs recall? Why don't we have the computer test us about things we're good at if part of the test has to be something only our individual brain is capable of?
Like, what if you pick the corpus of a novel that you've read as your master password. And the password manager uses that novel plus several other novels that you have selected (but didn't read/won't read?) to give you a series of multiple choice selections to determine if you know the right book. Just a few short passages. Preferably with proper nouns stripped out.
You have to select the passages from the correct book for all the multiple choices. That way rather than recall, the memory factor is recognition. Combine it with a non-memorable token which you have to present first in order to even see the recognition factor test and you might have something workable.
Maybe a low hit rate, but if you could automate it, you could run the scam on a lot of places.
Everyone wants Nix.
But we're not allowed to have Nix.
Because the world sucks and people look at something that has a little bit of necessary complexity and think, "I don't like complexity! I'll build something simpler", and they build it, and it looks cool because it seems simple, but then you use it and it turns out it has implicit complexity.
Chronos is the only one I'm aware of, but I don't believe it supports event based tasks.
I think Tor is releasing everything DRM free right now, but I'd like to see any stuff from other publishers that is also DRM free.
But I don't know if that's the only solution if being economical ends up being important.
Spike strips are really good at stopping cars, especially if they're running around a track in a circle.
That's a move that seems like it may push Gitlab ahead of GitHub in some ways (well, to me at least).
Is this 100% true? I don't know much about RF jamming, but isn't it sufficient to fix on the strongest source of the RF signal you're interested in and guide a cheap penetrator at it?
DARPA's Exacto bullets are doing that with optical guidance. Would it be that much harder with radio guidance?
I mean, that'd be funny, right? Teaching students something that you patented, waiting a few years for them to go into industry and apply what they learned, then suing them for it.
I dunno, this whole thing is weird. Generally I have to defer to people saying that the system isn't using enough energy to burn hairs, but unless the guy in question has had some sort of mental break or something, I don't get why he'd be involved with it if it was a straight fraud.
I don't know if he was actually involved in this project or not, but that was the one thing that made me think that this maybe wasn't 100% a scam?
Anyway, the implication they make in their pitch isn't that it's an open laser, but that it is a laser confined to a fiberoptic wire which leaks into the hair when pressed against it. Gustavsson has published some papers on this a few years ago in which he refers to the concept as a TRASER.
Of course, if this really is such a revolutionary advance, why go to Kickstarter to bring it to market? Why not traditional investors. Gotta be easier to get funding for a significant manufacturing outlay, right? Just to not have to sell a piece of the company? To justify that there is a market?
I personally don't have the background to make any judgments about this and I definitely don't understand the article he published, but I just thought it didn't completely fail the smell test.
I think my favorite stupid argument though is that it increases the size of the rider's head, which increases the likelihood of ground collision in an accident. As though it's so easy to stop yourself from falling as long as there aren't two inches of material strapped on your noggin.
The basic fact is that if you do have a head injury on a bike, a helmet is likely to reduce the severity of it. Everything else is an unquantifiable argument about human behavior.
Flywheels, compressed air, gravity storage?
Why not use some stuff like infant mortality or literacy or deaths from starvation or deaths from communicable disease? You know, stuff that actually indicates whether someone is impoverished or not.
I don't have a login on rust-lang yet, but I wanted to add this comment regarding the documentation:
The rust-doc auto generated pages are really confusing. The sidebar generally fails to show where in the hierarchy of the API docs you are (ideally it would highlight the current page you're looking at in the hierarchy and provide the full hierarchy to give you context), the breadcrumbs don't indicate that they are links, the breadcrumbs indicate the type of the entry to the left rather than the right adding semantic confusion, and long pages tend to not have a TOC meaning you have to either search in the page or know the page structure ahead of time (probably mostly an issue for new users).
I feel like those are all simple mechanical issues that could make the auto-generated rust-docs a lot more useful.
It'd also be nice to tie non-auto generated docs into a crate's documentation, but I haven't looked into how rustdoc works so I'd guess that's possible but a lot of people don't do it.
Which is my way of saying, "Doing good science is actually pretty hard."
To be mean to him: Deciding to split Foursquare into Yelp-lite and a shitty social network was a terrible, terrible idea.