shandor

19 ms·

151.
by shandor 9y ago
I think the most important point here is that with those different patch sets, the more security-conscious users/companies get to have the properly hardened version immediately into use, rather than running the "only report"
152.
Ask HN: How do you test your embedded systems?
3 points by shandor 9y ago|2 comments
153.
by shandor 9y ago
Impossible to answer in general context :) Nowadays anything from 16kB to 2GB of RAM gets called "embedded". Storage is the same but x10. I would be surprised if there's nothing to use Go for in all that design space, but ge
154.
by shandor 9y ago
It would be optimal if the team can have the discipline to never commit broken stuff, and we could live with "everything in master must be working all the time". If that does not work in reality, or breaking it would simply cost t
155.
by shandor 9y ago
My bad, I was going to edit my comment to be less coy and more constructive, but I'll just continue here. Even though I always advocate rebasing, I also think that WIP commits should not reach master as-is. We are actually using Phabri
156.
by shandor 9y ago
I always advocate workflows where merges never happen. To me, the 'git log' of a master branch is like a history book about the repository. When you read through it, it should give you answers to the questions "what was chan
157.
by shandor 9y ago
Sure, my meaning wasn't to talk down the project itself, it looks neat! The "MB does not matter" just jumped at me (somewhat out of context, I have to admit) since I work in the embedded land, and the pain is sometimes too re
158.
by shandor 9y ago
> Because MB don't matter I beg your pardon, but since Linux is increasingly used nowadays in quite resource constrained embedded devices, MB definitely does matter. (No, I don't claim that the individual 10 MB is very much on
159.
by shandor 9y ago
Thanks! That is quite surprising, and very encouraging. It seems that solar is a very good overall fit for even most of the world, and once the tech is good enough to be used in huge numbers the differences can probably be compensated with
160.
by shandor 9y ago
This is fascinating if true. Do you gave any sources, I'd be really interested in reading more on the matter.
161.
by shandor 9y ago
So what do avionics companies use? C, C++, Ada? Anything else?
162.
by shandor 9y ago
Sure you can, no one even implied otherwise. The only thing I said was that the term you are talking about most probably does not inspire the loathing it should (and once did) after all the crying-the-wolf. And considering that, I tried to
163.
by shandor 9y ago
I am not doing any of that. I'm just pointing out that this is a very real case of "crying the wolf" effect working it's voodoo, and that maybe, in the future, something could be learned from all this. Personally, I&#x
164.
by shandor 9y ago
One would think that, for the people calling Republicans "nazis" in the 2000's, the absence of swastikas and Nazi Hails should have cleared things up. But they did it anyway. People are not simple creatures, and things like c
165.
by shandor 9y ago
That's not the problem. The problem is that for many, the years and years of calling your run-of-the-mill Republicans and whatnot "nazis" has diluted the term, just like GP mentioned. So, now, when people try to get others to
166.
by shandor 9y ago
I think you're still missing the point. I understood that the author was criticizing the mindset of the companies which "want to use blockchain". In those cases, "moving the goal posts" is actually the sensible th
167.
by shandor 9y ago
That's...surprisingly simple. As it happens I was just today lamenting to a colleague that for all the blockchain hype, I have yet to hear about any other relevant use case than those which have an ideological agenda to require decentr
168.
by shandor 9y ago
> Almost nobody wants to work on the exact same thing for more than a few years unless it's genuinely super interesting That's a really, really tough problem actually. Businesses naturally want people to work on things that th
169.
Lessons from 20 Years of Hype Cycles (2016)(linkedin.com)
2 points by shandor 9y ago|0 comments
170.
by shandor 9y ago
Thanks, that was really interesting. Guess I'll have to go and read on mruby now!
171.
by shandor 9y ago
Embedded stuff in Ruby? Now that's a story I want to hear. Any pointers?
172.
Game of Thrones data leaked in HBO hack(nakedsecurity.sophos.com)
1 points by shandor 9y ago|1 comments
173.
by shandor 9y ago
The real problem relating to "profit" in these cases is that companies are not penalized at all for leaking their users' secrets, not the fact that security has "tradeoffs". Software industry is in the same boat reg
174.
by shandor 9y ago
This is so stupid. I mean, I don't need the apps, so any kind of coercion is pretty much doomed to fail. I don't usually need LinkedIn, and I definitely don't "need" Pinterest, ever. Making their websites suck mor
175.
by shandor 9y ago
> the DAO fork was a result of centralized control due to social factors. As with bitcoin, a >50% consensus is necessary to fork a blockchain I'm not very well-versed in computational power requirements on this scale, but it does
176.
by shandor 9y ago
I keep hearing about an inherent problem in this capability to "resist contentious changes". In dark corners it keeps whispered that if any one entity gets control over 50% of the mining capacity, they can essentially decide the &
177.
by shandor 9y ago
Seriously, the more complex your use case is, the better the command line gets. Personally, I use mostly command line git and on occasion a little bit of gitk if I get lost between all the branches. I die a little (read: a lot) inside when
178.
by shandor 9y ago
Thank you, this was the first comment actually telling more on the matter after all the "it said I'm X years old!" comments :) I guess using such a system just to analyze people in real-time might already violate some surveil
179.
by shandor 9y ago
I was just going to post a comment asking why your proposed way is not the standard way. Surely free is (usually) not called that often that the overhead would be anything close to unbearable? This seems like a so simple method of handling
180.
by shandor 10y ago
Me too, though I have them setup on shell rather than .gitconfig. Saves that one space after 'g' :) The ones I find myself using most are 'gru' for git remote update, and 'gka' for "gitk --all -500 &&q

More ›