Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
PeCaN
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
42 ms
·
361.
▲
by
PeCaN
10y ago
Eh? LuaJIT has got to be one of the best pieces of C I've read, and the documentation while scattered (mailing lists and wiki) is pretty solid.
362.
▲
by
PeCaN
10y ago
There was a lot of effort a couple years ago to fully port WebKit including HTML5 video, audio, etc. NetSurf also runs on Haiku, if you want something lighter weight but with enough rendering support for most sites.
363.
▲
by
PeCaN
10y ago
I can't say I speak for the “Haiku community” short of being friends with some of the developers and hanging in the IRC channel, but … no that's not a common attitude. Haiku prefers non-copyleft licenses, but doesn't avoid th
364.
▲
by
PeCaN
10y ago
Haiku is pretty damn fast. Its kernel (NewOS) was written by one of the BeOS developers and the whole system's architecture is generally pretty similar to BeOS.
365.
▲
by
PeCaN
10y ago
…That's actually one of the things I like about Photoshop—you can just press Ctrl-Z repeatedly to look at before/after a change. Sure it's odd, but there's a reason it's the way it is.
366.
▲
by
PeCaN
10y ago
It doesn't. GIMP's support for nondestructive editing is very primitive, which might be the biggest issue. In terms of tools PS is far more comprehensive and flexible. GIMP is more like Paint.NET than Photoshop.
367.
▲
by
PeCaN
10y ago
APL-style with a global index origin ($[ in Perl, à la ⎕IO in most APLs).
368.
▲
by
PeCaN
10y ago
Yeah, it would be really hard to change all the millions of documents written with QWERTY.
369.
▲
by
PeCaN
10y ago
Nope.
370.
▲
by
PeCaN
10y ago
There's something amazing about the fact that the entire Red system, including GUI framework, parser DSL, runtime, and compiler for a C-like language (Red/System) is smaller than the average webpage . (Red—the entire thing—is a s
371.
▲
by
PeCaN
10y ago
There's not really any evidence for or against that. On lower-resolution screens, sans-serif fonts may be more readable for longform, since serifs often get a bit fuzzy.
372.
▲
by
PeCaN
10y ago
Using “them” when you already clearly know the gender is bad style stemming from political-correctness zealots.
373.
▲
by
PeCaN
10y ago
See also the Portia spider, which is somehow capable of planning ahead and following prey even when it's out of sight. http://news.nationalgeographic.com/2016/01/160121-jumping-sp...
374.
▲
by
PeCaN
10y ago
Is “make a pretty generic RISC processor and license it” really “disruption”? ARM didn't do anything especially novel, they did one thing really well. They read the Berkley SPARC papers and made a simple CPU. It's the same thing a
375.
▲
by
PeCaN
10y ago
#proglangdesign and #osdev are some of my favorites on Freenode, otherwise it's mostly language-related ones. #dragonflybsd on efnet is probably my favorite technology-specific channel. Lots of interesting stuff happens there (and sage
376.
▲
by
PeCaN
10y ago
BeOS and OS 9 were well designed. I feel like we've sort of lost our way about what made those OSes good, replaced it with very “showy” graphic design. Operating systems should be a tool for information and communication, not a modern
377.
▲
by
PeCaN
10y ago
Heaven forbid a company tries to save money AND do research…
378.
▲
by
PeCaN
10y ago
The funniest part is that the C in K&R is not really much different, let alone better, than in any of the books they recommend against. I guarantee K&R would be on their list of books to avoid if it wasn't written by… well, K&a
379.
▲
by
PeCaN
10y ago
If that's from the freenode ##c wiki, you should probably take that as a ringing endorsement. ##c is laughable. I'm not sure they actually use C, or just think about the C Abstract Machine and Glorious Specification.
380.
▲
by
PeCaN
10y ago
My browser gets messy and I tend to lose the Slack tab. I could just pin it I suppose.
381.
▲
by
PeCaN
10y ago
Yeah, and they're both pretty miserable. I'm thinking of unsubscribing to Spotify just because their desktop client is so bad. Also, I'm not sure why Slack needs ~250MB of RAM. Seems a bit extreme for a chat app.
382.
▲
by
PeCaN
10y ago
Heh, that's exactly what I do like about D—the generic programming/metaprogramming paradigm instead of OOP. You can get some very elegant and efficient code with D, while OOP tends to have more runtime overhead.
383.
▲
by
PeCaN
10y ago
Really? I loaded a 1.2GB ISO in the demo and it used… 1.2GB of RAM. (At least it worked though, cough Atom cough .) And more importantly it has no unicode support whatsoever as far as I can tell (any non-ASCII characters I typed showed u
384.
▲
by
PeCaN
10y ago
Why do you prefer it over regular Emacs? How is it better enough to make up for the much larger collection of extensions for Emacs? The demo for me just felt like a snappier Emacs clone.
385.
▲
by
PeCaN
10y ago
Its extension language looks very interesting. It looks very powerful while having domain-specific features (I've noticed ‘user’, ‘command’, and ‘save_var’ keywords). See e.g. http://www.lugaru.com/ftp/for-v13/
386.
▲
by
PeCaN
10y ago
Project Denver still JITs ARM to an internal VLIW architecture I believe. It's pretty Transmeta-like.
387.
▲
by
PeCaN
10y ago
That was Transmeta, which became Nvidia's Project Denver. I think the show stopper is that they were unable to acquire an x86 license. Anyway, it actually ran neither (the core is more like Itanium) and had a separate chip that JIT com
388.
▲
by
PeCaN
10y ago
Especially in the same word! cough television cough
389.
▲
by
PeCaN
10y ago
Well, people smarter than me at Google and IBM seem to think D-Wave works, so I sort of skeptically believe it for now.
390.
▲
by
PeCaN
10y ago
Nearly all x86_64 instructions are microcoded on modern Intel and AMD CPUs. That does not mean they're slow. Some instructions may end up slow when the microcode isn't updated to take advantage of the latest processor iteration
More ›