alblue

13 ms·

61.
by alblue 6y ago
Yes, prior versions were insanely buggy. 1.0.2 was pretty stable as they fixed most of the problems by then, although Java 1.1 was when companies started to really use it for stability. Problems happened with the windows fork which was pinn
62.
by alblue 6y ago
Java bytecode allows for Debug attributes, which are produced by default in most build engines, and say which field maps to which item on the stack and for how long. Even if that information is removed, the fact that you have the return val
63.
by alblue 6y ago
No, it's likely that it won't be quite as disruptive in the future. There were a few backward incompatible changes with modularisation (in order to break module cycles) but the bigger disruptive changes were moves away from sun.mi
64.
by alblue 6y ago
I gave a presentation on bytecode and class loaders if you’re interested. The deck is at speaker deck and there’s a link from there to a recording I did for the LJC if you prefer me narrating it: https://speakerdeck.com/albl
65.
by alblue 6y ago
What's even more interesting is that C++ and Objective-C started around the same time, and while one is known about widely, the other is still used heavily in the macOS and iOS ecosystems today. Indeed, the creator of Java acknowledged
66.
by alblue 6y ago
I've written up a more detailed piece at InfoQ: https://www.infoq.com/news/2021/01/java-turns-25/
67.
Java 1.0 Turns 25(infoq.com)
230 points by alblue 6y ago|260 comments
68.
JavaSoft ships Java 1.0 (1996)(web.archive.org)
26 points by alblue 6y ago|1 comments
69.
by alblue 6y ago
The Goldman office is not fully staffed any more, and many bankers are leaving for Europe. The euro market has gone already, and others aren’t far behind. https://www.bloomberg.com/news/articles/2021-01-15/bre
70.
Why “i” is used in for loops(twitter.com)
3 points by alblue 6y ago|3 comments
71.
by alblue 6y ago
The last “word” in the title needs updating to have some space in it so it breaks properly on mobile devices.
72.
Steve Bannon’s WarRoom Banned from YouTube(twitter.com)
23 points by alblue 6y ago|4 comments
73.
by alblue 6y ago
Yup, my presentation was back in March 2020 and the M1 came out later in the year — sooner than I was expecting, TBH; I thought that it was a couple of years out when I said it :-)
74.
by alblue 6y ago
The problem is that leap seconds might have made sense when time keeping was accurate at the millisecond level but now that time can be measured at the nanoseconds level (at the speed of Computing, essentially) such changes are to big and c
75.
by alblue 6y ago
Swatch tried to do that by creating Swatch Internet Time, which was a time zone less decimal time system. As you can guess, this didn’t end well or take over the world. https://en.m.wikipedia.org/wiki/Swatch_Internet_Ti
76.
by alblue 6y ago
I have never seen that term be used in this way before, nor can I find any references on that. Do you have links to be able to justify this claim?
77.
by alblue 6y ago
See also https://twitter.com/TwitterSafety/status/1346970433917222912
78.
by alblue 6y ago
It can be mitigated somewhat if you have pcid enabled for the processors, so that a flush can be process specific instead of cpu-wide. There’s still a performance hit of course but you’re going to lose some locality with a context switch an
79.
by alblue 6y ago
Sort of; Intel and AMD are stuck with the variable width instruction isa that exists due to historical evolution. To do something different you need a new isa. Intel tried this with Itanium a while back and failed because it is difficult to
80.
by alblue 6y ago
This isn’t specific to the M1 but I tap about cache lines in my last QCon presentation (where I also suggested that a 128b cache line wasn’t far away): https://www.infoq.com/presentations/microarchitecture-modern... Ho
81.
by alblue 6y ago
To be clear here, it fetches two cache lines but it doesn’t put the second in exclusive state until it’s written to; the unit of granularity is still 64b. In a scanning read mode you will see the benefit but you won’t see the contention on
82.
by alblue 6y ago
The big problem with the nightingale hospitals is that there were no staff to run them, and hospitals are understaffed as it is with people of sick or isolating due to the governments approach of vaccinating their voters first ahead of medi
83.
by alblue 6y ago
Interesting paper, but I noticed a couple of typos: * ntel in the conclusion * x96 in the main body (in case the paper authors read this commentary)
84.
by alblue 6y ago
Indiana Jones and the Crystal Skull has what turned out to be aliens and an alien spaceship.
85.
by alblue 6y ago
Time to emigrate from the U.K. to a more enlightened country. What countries would you go to as an English expat for a better life? Where can you change a useless English citizenship for another?
86.
by alblue 6y ago
Not really. Under the covers, it has always been an object database where the objects key is the hash of that object, and other than blob, tree, commit and signed tag they haven’t really changed since then. The protocol has become a bit sma
87.
by alblue 6y ago
That only works when your SVN server is in the same computer as you; the fact that SVN has to reach out to get additional data for the history is what kills it. With git on the other hand, all the file storage is local to you machine regard
88.
by alblue 6y ago
Longer exposure, but the lights in the room were dimmed as well to allow it to show up. The brightness was pretty limited. No filter used other than the iPhone native camera in low light conditions.
89.
by alblue 6y ago
I took a photo of it when I was at the computer history museum last time: https://twitter.com/alblue/status/1340463649597616128
90.
by alblue 6y ago
Al Lowe is on Twitter at @allowe if you’re interested, and has a site at allowe.com. I can also recommend the Ken Williams book, by the way.

More ›