Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
gioele
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
65 ms
·
571.
▲
by
gioele
14y ago
Because SPDY has well known flaws (let's call them design choices) for example in caching. There have been many discussions in HN about these topics. Also, because there is no such a thing as "SPDY" what you are referring to is "SPDY 2 as i
572.
▲
John Carmack: Sorry for borked release; console vs PC; VR headsets revolution
(youtube.com)
1 points
by
gioele
14y ago
|
0 comments
573.
▲
by
gioele
14y ago
> I see no benefit. The first benefit is that it removes clutters from your $HOME. The second benefit is that you can now manage and backup your settings in a sane way. * ~/.config contains config files (should not be lost, but if lost
574.
▲
by
gioele
14y ago
Paraphrasing Tim Bray, selling bags of bits is probably not a good business model for most of the people. (Unless you have draconian DRM measures in places.)
575.
▲
by
gioele
14y ago
Having `restrict` in the function declaration allow other tools to know about the aliasing constraint without the need to read and understand the function code. Think of documentation tools, static checkers, code completion functionalities
576.
▲
by
gioele
14y ago
> a device that isn't selling much anyway. In EU, Samsung Galaxy Tabs (either 10 or 7) are the only non-iPad tablets I've seen in the hands of not technical people. Most phone carriers offer cheaper mobile data plans bundled with a Gala
577.
▲
by
gioele
14y ago
For all the lovers of the "prefixes are not useful, just do without them": > Also the <angle> changed: before, 0deg pointed to the right; now it points, consistently with other angles in the CSS spec, to the top.
578.
▲
by
gioele
14y ago
So you have to pay to get what installing unbound (Win, OSX, Linux) on your machine will give you for free?
579.
▲
by
gioele
14y ago
«All of which leaves just one question: what has the W3C ever done for us?» It has given us good specs fixed in stone you could develop against and be sure that your code could still work in the next decade, thing XML or XSLT. Stable specs
580.
▲
Fundamental Unicode in Perl
(speakerdeck.com)
3 points
by
gioele
14y ago
|
0 comments
581.
▲
by
gioele
14y ago
Link to the patent, no Flash required: http://www.google.com/patents/US6857067
582.
▲
by
gioele
14y ago
> My understanding is that the app must be fullscreen, and the user can always escape fullscreen and pointer lock with the ESC key. It is similar in other windowing systems. But, but... You are in fullscreen mode with a pointer grab. An
583.
▲
by
gioele
14y ago
Yes, browsers should take responsibility for doing it without asking the web devs to handle it, with the possibility of messing it up. Operating systems have spent years dealing with power saving policies and application requests for keepin
584.
▲
by
gioele
14y ago
Yay, pointer grabs in user-supplied code! What could possibly go wrong? https://encrypted.google.com/search?q=x11+mouse+grabs+proble... For those not familiar with the problems: pointer grabs are notorious for being a pain to deal with. T
585.
▲
by
gioele
14y ago
> he's already lost ground to SPDY just because they've shipped code. Is SPDY good enough now and fixable enough in the future to leverage this gained ground? As more and more people deploy SPDY, they will understand its problems and th
586.
▲
by
gioele
14y ago
And a PDF with a comparison of all those 39 models http://omgfire.narod2.ru/SBC_comparison39.pdf
587.
▲
The setuid patent (Dennis Ritchie, 1979)
(patft.uspto.gov)
1 points
by
gioele
14y ago
|
0 comments
588.
▲
Camera tracks and centers fast moving objects
(k2.t.u-tokyo.ac.jp)
3 points
by
gioele
14y ago
|
0 comments
589.
▲
Varnish author finds "the design approach taken in SPDY deeply flawed"
(varnish-cache.org)
3 points
by
gioele
14y ago
|
2 comments
590.
▲
by
gioele
14y ago
Too many words to express what The Ultimate Productivity Blog already said three year ago. http://productiveblog.tumblr.com/ PS: ;)
591.
▲
by
gioele
14y ago
This comment on Slashdot highlights how Apple is making recycling much harder, not "doing more than the EPEAT guidelines required". http://apple.slashdot.org/comments.pl?sid=2970727&cid=40... «Recycling is NOT dumping it in a landfill
592.
▲
by
gioele
14y ago
> The latest published version of the standard (5.0) runs to almost 1500 pages: Most of those pages are the just repertoire: a printout of a long uneventful table that lists all the available code-points. For each code-point is gives yo
593.
▲
by
gioele
14y ago
> So contrary to your comments, they're doing this because the W3 said that it's time to do so. My point is that support for prefixed CSS properties should not be available in stable releases at all. What they should have done from the
594.
▲
by
gioele
14y ago
I hope I will not see many more of this kind of news. Dear browser makers, please, enable your prefixed CSS properties only in dev/night/beta builds. Leave only unprefixed CSS properties in the release stable browsers. With this you will be
595.
▲
by
gioele
14y ago
Two problems: perfomance and premature abstraction. Using function pointers instead of direct calls one drastically reduces the ability of the compiler to optimise function calls. Second, in most architectures calling a function through a f
596.
▲
by
gioele
14y ago
Discussion thread on LWN (with the author, Richard Fontana): https://lwn.net/Articles/505589/
597.
▲
by
gioele
14y ago
Boundary value analysis? Machine state transitions testing? Equivalence partitioning? There are heaps of techniques one can use to identify which data points and combinations are useful to test. Some of these techniques even take a peek at
598.
▲
by
gioele
14y ago
Why an extension and not a greasemonkey userscript?
599.
▲
by
gioele
14y ago
While this is true for bigger design issues, I fear it is not true for smaller problems like off-by-one accesses and all the common parsing issues. Smaller problems require a lot of time, attention and testing to be found. To have a single
600.
▲
by
gioele
14y ago
It is nice to see that we are moving from huge and clumsy DNS servers (BIND) to smaller servers with a specific focus: unbound as resolver, NSD/Yadifa for authoritative servers. Now that we have them, couldn't some core code be shared betwe
More ›