faragon

52 ms·

541.
by faragon 10y ago
Sure. That was my point: the "New Microsoft" is not using Linux, or don't {care about | want} their customers using "New Microsoft" products on Linux.
542.
by faragon 10y ago
Amazon is too big to fail.
543.
by faragon 10y ago
So engineers at "New Microsoft" read Hacker News, but don't use "New Microsoft" products on Linux.
544.
by faragon 10y ago
So for the "New Microsoft" releasing a bug fix for a "bug" affecting customers using Linux for more than 3 months it just required to be popular at Hacker News and Reddit.
545.
by faragon 10y ago
Any official explanation from the "New Microsoft"?
546.
by faragon 10y ago
Main difference, IMO: now you're at least 10 times more productive. No waiting for floppy discs nor 75-125KB/s hard disks (!), better tools (better SCMs, compilers, etc.), using the Web for searching (ideas, fixes, help, etc.). If
547.
by faragon 10y ago
LynxOS (hard RTOS) is quite nice. I hope Linux gets hard real time support for userland, some day :-)
548.
by faragon 10y ago
How they do show sorted data when not having a tree, but hashes?
549.
by faragon 10y ago
So finaly we're going to get from Intel what HP promised years ago as "memristors".
550.
by faragon 10y ago
Realloc, if well implemented, does not copy (using virtual memory stuff).
551.
by faragon 10y ago
It was just curiosity for that corner case. Obviously, for handling many small memory elements, it is better to avoid calling allocators as much as possible, e.g. using one linear allocation for all the elements, and using realloc() with ge
552.
by faragon 10y ago
That's wonderful. For non-cryptographic uses, this could speed-up a lot of things, e.g. even git, replacing the SHA1 with a e.g. a 128 bit hash made from a xxHash64(file_content)) plus the size of the file (64 + 64 bit). In fact, repla
553.
by faragon 10y ago
Anyone has measured what takes to free a big amount of small reserved blocks at once, e.g. free 10^8 blocks of 16 bytes?
554.
by faragon 10y ago
That is insane. One thing is having poor performance because of the lack of specific processor support, and another not being able to use it at all. Is there a bug in those new processors with backwards compatibility, or is it an evil move
555.
by faragon 10y ago
I can't wait for Facebook, or LinkedIn, selling "backchat protection" or equivalent...
556.
by faragon 10y ago
Also a Programmers' Word Processor, indirectly: Borland editors (Turbo Pascal, Turbo C, etc.), JOE, and others, took many of the WordStar key combinations... [1] [1] http://texteditors.org/cgi-bin/wiki.pl?WordStarF
557.
by faragon 10y ago
In my opinion, the main problem with "OOP", and other contemporary religions, e.g. "design patterns", "TDD", etc., is that often you face arguments like "with me, or against me", like if there were no
558.
by faragon 10y ago
Well, one-time 250.000 USD donation for a company like Intel, is quite small, in my opinion, considering most FreeBSD servers are running Intel CPUs.
559.
by faragon 10y ago
Very useful work! I would love to see it implemented in many other languages. Any takers? :-)
560.
by faragon 10y ago
Sure. And also, may be the Google-Inte Skylake comes from past year, when Google was testing POWER9 chips... [1] [1] https://www.theregister.co.uk/2016/04/07/open_power_summit_p...
561.
by faragon 10y ago
Which patent applies to Zstandard?
562.
by faragon 10y ago
Prior to being into Facebook's GitHub, it was into a Yann's GitHub, with different license terms. Someone could fork it, keeping the compatibility with the latest API. It could be enough for FB being pragmatic and releasing it und
563.
by faragon 10y ago
And what about an artificial moon instead?
564.
by faragon 10y ago
1/33? [1] [1] http://www.columbia.edu/cu/computinghistory/superbrain.html
565.
by faragon 10y ago
1KiB of RAM (1024 bytes) is 8 times the RAM of the Atari VCS/2600 (1977).
566.
by faragon 10y ago
UTF-16 has reserved codes as well, so it could be expanded for covering 2^32 codes, too.
567.
by faragon 10y ago
Sure, that's why I pointed it could be expanded anytime, because the encoding already supports its expansion, by design :-)
568.
by faragon 10y ago
UTF-8 encoding could use up to 6 bytes per character, addressing up to 2^32 codes (UTF-8, 1993 version [1]). So even being currently limited to 4 bytes, it could be expanded to 6 anytime. [1] https://en.m.wikipedia.org/wiki&
569.
by faragon 10y ago
"Cerebro" in Spanish means "brain".
570.
by faragon 10y ago
Being aware about the Dunning–Kruger effect [1], focus in deliver instead of blindly following brain-dead process religion/s (put your favorite agile/religion here), and learn to identify the best possible talent so you can work w

More ›