Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
capisce
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
151.
▲
by
capisce
13y ago
Ignored the "Do not exceed the recommended dosage" warning eh?
152.
▲
by
capisce
13y ago
He was hiring a remote filipino worker and his dutch friend apparently.
153.
▲
by
capisce
13y ago
A big reason for the Tesla Model S being the best selling car last month is that a lot of people have been on waiting lists for months to buy one, and they only started selling them in August. Not to say that it won't keep selling well
154.
▲
by
capisce
13y ago
That's a shame, considering how cheaply GPUs can do it these days.
155.
▲
by
capisce
13y ago
Same here, just recently broke my Nexus 4's display. Doesn't seem to be easy to get it repaired either...
156.
▲
by
capisce
13y ago
A job being boring is just one of the reasons you might get paid to do it. Another reason could be that it's hard and that you are one of the few available for hire with the necessary skills. Then it can still be all fun (for you). I t
157.
▲
by
capisce
13y ago
Epäilemättä.
158.
▲
by
capisce
13y ago
Having to go through the form hell of filing US taxes seems like a tax in itself.
159.
▲
by
capisce
13y ago
I tried to buy it but it didn't look like you could preorder an e-book
160.
▲
by
capisce
13y ago
17) Machines increasingly produce items in a cheaper, safer, and more robust way than people 18) In time there will be nothing worth paying a person for that a machine can't do cheaper or better 19a) People will need to work less and l
161.
▲
by
capisce
13y ago
Aren't you worried about missing out on the best performing hires then? Why would a person who can pick and choose work at a place where ass-in-seat time is used as a metric?
162.
▲
by
capisce
13y ago
Let's not stop there: http://www.neweconomics.org/publications/entry/21-hours
163.
▲
by
capisce
13y ago
On the other hand, I see a developer's tools as an extension of his or her mind. Enforcing that everyone uses the same tools seems like a great way to encourage hive mind thinking. Especially proprietary tools that can not be automated
164.
▲
by
capisce
13y ago
A problem is when those big businesses prevent other smaller businesses from catering to the niche markets, through lobbying or other anti-competitive means.
165.
▲
by
capisce
13y ago
We call this a leaky abstraction :)
166.
▲
by
capisce
13y ago
Shouldn't a language for sharing UI be human readable like QML ( http://en.wikipedia.org/wiki/QML#Basic_syntax ) instead of machine readable like XML with its claustrophobic tag soup mess, flow killing end tags, a
167.
▲
by
capisce
13y ago
Or just use QML: http://en.wikipedia.org/wiki/QML#Basic_syntax
168.
▲
by
capisce
13y ago
Maybe I should give emacs/slime another try then. I use paredit in vim already, but I guess I could give redshank a go. What I like in vim is shortcuts like "ca(" or "ci(" to change an s-expr or change the contents
169.
▲
by
capisce
13y ago
pico and nano are certainly easier to use and have a much less steep learning curve, but they can hardly match the efficiency with which I can refactor and edit code using vim
170.
▲
by
capisce
13y ago
I've tried using emacs/slime with evil but currently I prefer vim/slimv. Evil just felt a little bit "off" compared to regular vim, or maybe it was the slime integration. Anyhow, I recommend giving slimv a try, ther
171.
▲
by
capisce
13y ago
Ah, I didn't know PNaCl didn't have explicit SIMD through vector types yet. Sounds like it should be relatively easy to add though since LLVM already provides them.
172.
▲
by
capisce
13y ago
First of all clang and LLVM support the GCC vector extensions which means you can write portable SIMD code: http://clang.llvm.org/docs/LanguageExtensions.html#vectors-a... Second, compilers also do auto vectorization (automatically vector
173.
▲
by
capisce
13y ago
"within 2x the speed of native" Of crippled native, with things like SIMD instructions disabled.
174.
▲
by
capisce
13y ago
The Unreal Engine demo does pretty much all of its work on the GPU.
175.
▲
by
capisce
13y ago
With the trade off that the code size is greatly increased and that the performance when falling back to pure JavaScript will be dog slow. If the performance of an application is only acceptable on the subset of browsers that implement asm.
176.
▲
by
capisce
13y ago
Except LLVM bitcode seems much more able to expose the cabilities of the underlying CPU compared to asm.js. I guess we'll just have to wait to see what the benchmarks say.
177.
▲
by
capisce
13y ago
I fear the limitation that it has to be a subset of JS must lead to performance trade-offs, through the lack of 64-bit integer types or single precision floating point / SIMD vector arithmetic for instance.
178.
▲
by
capisce
13y ago
PNaCL seems like a much saner stack, turning JS into assembly never made sense to me if you want to get the most out of the hardware (with resulting power savings and/or performance gains).
179.
▲
by
capisce
13y ago
Yeah, it sounds very dubious to me that the amount of code in Go ends up being much less than what's required to achieve the same in Lisp. From what I've seen Go looks verbose in comparison with the lack of macros and higher level programmi
180.
▲
by
capisce
13y ago
> Go is not a language focused around individual productivity in any capacity or scope. Seems to have been my impression as well. Lisp with its macros can make an individual programmer who doesn't need to worry about coding conventions
More ›