Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
weland
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
29 ms
·
211.
▲
by
weland
12y ago
> I honestly don't see a difference except in degree (and hence in jail time I'd prefer to see resulting from actions based on each of the attitudes, roughly 15 days and 15 years, respectively.) Except for that thing about huma
212.
▲
by
weland
12y ago
Meet marketing. I will personally buy pizza for one week to any marketing department that, when announcing a new product, publishes figures that are actually useful. Oh look, we just launched a MCU with a power consumption so low that you
213.
▲
by
weland
12y ago
This is very true. At that time, even 68K-based workstations ran circles around any x86-based design. x86 was, however, cheap, high-volume and with a lot of compatible hardware, so there was sufficient interest to pour resources into it.
214.
▲
by
weland
12y ago
This is likely intended to be use with batteries that can recharge from very low-energy sources, e.g. energy captured from the body. It has very small energy consumption in sleep mode, so the battery can charge between wake cycles. 200 nA i
215.
▲
by
weland
12y ago
It's not even new. It has a 40-year history and unikernel-like systems were a major research topic during in the late 80s and early 90s -- except everyone was dreaming that we'd have thousands of tiny machines to run it on, rather
216.
▲
by
weland
12y ago
If you read the articles closely, you'll see that they're anything but "alleged". The "morality" dasil003 mentions, which "does not agree with that of the wider culture surrounding them", disagrees wi
217.
▲
by
weland
12y ago
> Perhaps you mean their morality does not agree with that of the wider culture surrounding them. Absolutely. The Western civilization is ignorantly missing things like the incredible cultural value of sexual abuse ( http://ab
218.
▲
by
weland
12y ago
> Maybe in really limited embedded systems. Given the incredible complexity of C++, I would much rather see Rust or Go come to those systems rather than C++.
219.
▲
by
weland
12y ago
I mean, when it's so huge, there's bound to be some good parts in it, you just have to look for them a lot.
220.
▲
by
weland
12y ago
Am... I missing a color picker there?
221.
▲
by
weland
12y ago
> IMHO you havent seen https://extensions.gnome.org/ . Of course I've seen https://extensions.gnome.org/ , Gnome is almost unusable without it. But Gnome extensions aren't supported by the core
222.
▲
by
weland
12y ago
Pretty sure I didn't take OS X as an example of how it's done. In fact, I took it as an example of how it's not done, which is why I find it unpleasant that Gnome is following in their footsteps. > The position of the wi
223.
▲
by
weland
12y ago
> It is harder to breach two layers of security at the same time than one. I think sandboxes are easier to realize than, say, a secure browser. I'm not questioning the advantages that sandboxing seems to have, in general. What I a
224.
▲
by
weland
12y ago
> Even with open applications there is an additional security layer which is _very_ valuable because security related bugs are the normality, not the exception. Considering that regularly writing secure servers or browsers seems to be be
225.
▲
by
weland
12y ago
I have very mixed feelings about some of the stuff Gnome is doing. Some of them are at least interesting from a certain point of view, like sandboxing applications. I get why this would be nice to have in corporate environments, and that
226.
▲
by
weland
12y ago
I'm thinking strictly about the customization of the UI, not of "everything else" in System Preferences (e.g. hardware, network and so on). You can set individual icons but you don't have icon themes per se, can't c
227.
▲
by
weland
12y ago
KDE is a breath of fresh air in the current Linux desktop space. It gives you all the nice integrated tools that Gnome gives you while not trying to make you part of a Borg collective and actually (gasp!) listening to its user community.
228.
▲
by
weland
12y ago
I use wget for plain, old regular downloads a lot. If I need to save a file to a specific place (e.g. datasheets to a doc/ directory in my project) and I have a terminal already open there (which I usually do), doing wget and middle-
229.
▲
by
weland
12y ago
Technically yes (although, by default, no), but it's more efficient than that would imply. By default, I think only small chunks are overwritten, so OpenSSL's meagre 64 KB of Heartbleed payload would have been filled with useless
230.
▲
by
weland
12y ago
If you follow the same faulty line of reasoning about performance and portability that led the OpenSSL team to introduce their incorrect wrapper over native malloc(), you will find that you'll reproduce Heartbleed using entirely safe c
231.
▲
by
weland
12y ago
The section responsible for Hearbleed was never allocating more than 64 kilobytes , which can probably be cleared in 1000 cycles on most modern architectures. As someone else pointed out, OpenBSD's malloc() implementation could have s
232.
▲
by
weland
12y ago
It's extremely important to remember this in context: Heartbleed occurred on OpenBSD because OpenSSL had its own wrapper over malloc(). Instead of actually free()-ing those areas when calling openssl_free(), OpenSSL would leave them
233.
▲
by
weland
12y ago
A good portion of LibreSSL's patches are in the form of removing code for dead platforms like VAX/VMS and OS/2, problematic wrappers like openssl_malloc() or patching the everything-on-by-default approach that OpenSSL takes.
234.
▲
by
weland
12y ago
IMHO, the "connectivity for everyone" thing is a thin cover of "controlled distribution channels for anyone who can't afford better". > people won't care about the few MBs/month it costs them. This init
235.
▲
by
weland
12y ago
Yes, my point was that OpenSSL did not throw away the standard library! openssl_{malloc|free} were thin wrappers over the native malloc() and free(), except that they tried to be clever and not natively free() memory areas so that they
236.
▲
by
weland
12y ago
Ah, crap, I saw your reply only now :(. The Plan 9 documentation is pretty good, but 9front's introductory documents ( https://code.google.com/p/plan9front/wiki/fqa ) are probably a little better to get
237.
▲
by
weland
12y ago
It doesn't have custom allocator support as in "you can't have one function allocate memory and pass it for another function to use it", or as in "you can't replace the runtime's own malloc"? OpenSSL
238.
▲
by
weland
12y ago
> I really disagree. Rust does not allow uninitialized values by design - end of story. If a piece of Rust code let's uninitialized values bleed through, then it is broken. The semantics of Rust demands this. (OpenSSL on the other h
239.
▲
by
weland
12y ago
That comment sort of illustrates my point: > You should note that Rust does not allow unintialized value by design and thus it does prevent heartbleed from happening. But indeed no programming language will ever prevent logic bugs from h
240.
▲
by
weland
12y ago
> I'm amazed that you say that calculus has had a much greater impact on society when virtually every database, graphics manipulation or economic analysis uses principles of linear algebra. Studying any kind of engine (or for that m
More ›