Software developer & entrepreneur. Co-founder and CEO of Katoid. Author of ViEmu. Enthusiast of computation, languages, analytics, games, graphics, devtools, linguistics, AI, and software marketing & sales. Also of spelunking spaghetti codebases (sometimes) to try to turn them into gold (rarely).
I also love writing and performing music and comedy. Couldn't live without those.
I was around in that era and having to pay for assemblers, compilers, etc... didn't sound strange at all. What was also a reality was the difficulty of actually getting them if you were far away from the US (Spain in my case). The world was way bigger back then in so many ways.
Each CPU core doesn't have it's own independent channel to memory, there are usually 2-3 channels to DDR memory shared by all cores via multiple intermediate caches (usually shared hierarchically).
Not really. "I adore you" is literally "te adoro". "Querer" in Spanish just means "to love", it's a synonym to "amar", also "to love". "Querer" is more common language and applied non-romantically all the time, and "amar" is more poetic and veers more towards romantic love, but they both mean the same. BTW, "querer" means "to want", but when it is used to convey love (easy to tell by context), it doesn't ring of objectification in any way. "Quiero a mi familia" is the simplest, clearest, way to say "I love my family".
Not only the reader and the compiler, that kind of threaded code really helps performance thanks to leveraging the CPU's branch target buffer to obtain great branch prediction of interpreted code, and that is one of the killer aspects to get current CPUs to perform well.
There was travel and commerce between far out regions in that period (1,500-3,500 BCE). The connection between the three old-world starts of writing (Sumerian, Egyptian and Chinese) is, AFAIK, not 100% clarified yet. It's widely accepted that American writing was a separate original invention, it makes sense. I believe these days the accepted understanding is that Egyptian hieroglyphic writing is an independent development that may, or may not, have been inspired by Sumerian writing. Not hard to believe: "you know son, these peoples far far away know magic, they're able to make dents in a table containing a story, and then pass on the tablet to someone else and they can retell the story!" Chinese writing may, or may not, have also come up the same way.
Not to mention the cable deterioration. I recently got an M1 MacBook Air and the USB-C charger is finally designed such that the cable is replaceable. No admission of wrongdoing, blaming the user, but at least an acceptable final fix.
Thank you, note taken, that is very valuable information! OpenSSD is at least a good starting point to research and prototype, even if manufacturer help is needed later.
Hey that's very interesting! How much of the FTL logic is done with regular MCU code vs custom hardware? Is there any open source SSD firmware out there that one could look at to start experimenting in this field, or at least something pointing in that direction, be it open or affordable software, firmware, FPGA gateway or even IC IP? I believe there is value in integrating that part of the stack with the higher level software, but it seems quite difficult to experiment unless one is in the right circles / close to the right companies. Thanks!
It was brittle beyond belief. The process would run out of memory and crash really easily. You are supposed to dimension resources well, but of course you'd like to handle things more gracefully when a huge inflow of data or requests comes in, good engineering is "graceful failure" such as just rejecting requests, instead of total mayhem and destruction. It was "interesting" to discover that the monitoring plugins included by default would bring down the entire cluster. 5 beefy AWS machines brought down when pointing their own monitor at them! Yes there was significant input traffic, but I would expect more solid behavior from production-ready software.
Shard migration and duplication was a beauty to watch when it worked well, but very often it wouldn't. I tried to establish a procedure to bring instances back up safely and repeatably, but sometimes I would just have to try and try again, no procedure guaranteed restoring operation in all cases. I do remember spending more than one weekend babysitting that cluster. There's a special place in my heart for that memory, and it's not a beautiful one.
I was very surprised to see them IPO successfully - this test was before they were public. I assumed the open source version was just missing the kind of tools and know how to be able to work solidly without paying them or their consultants. These days, I think it's poor engineering resulting in brittleness, we shouldn't have put so much traffic to it, and probably everyone out there experiences the same behavior unless they ensure much safer margins, which probably makes it expensive but I guess who's complaining.
I ended up designing and writing my own (much simpler) distributed system for what I needed (much simpler than everything ElasticSearch does, of course), and it's been in reliable operation since summer 2015. Good engineering goes a long way. Now in the process of turning that approach into a startup. If I get 1/10th as successful as ES I will be a happy camper :)
Lucene is Java, right? There should be space for a native implementation, like ScyllaDB is doing to Cassandra (and DynamoDB, though the gap is not of the same shape in the last case). Or am I missing something?
I used ElasticSearch and run one cluster in production in the past and found it horrible. Maybe I'm missing something, since they're so successful even as a public company...
The two cores only share FP and vector execution units. A ton of code doesn't use those at all, and so they are effectively two separate cores most of the time. It provides full compatibility on both cores, full performance very often, and saves a lot of die area (FP and vector are going to be very transistor-heavy). It's just a tradeoff.
From the article, it seems the problem was that the CEO wasn't authoritarian enough, rather than the other way around. Looking to build consensus, rather than strongly setting direction. But I guess that's also just one piece of the puzzle too.
Very interesting description. Are you familiar at all with the details of FPGAs for these very same tasks, especially the EV family of Xilinx Zynq Ultrascale+ MPSoC? They include hardened video codec units, but I don't know how they compare quality/performance-wise. Thanks!
Very interesting, I am familiar with many of the concepts and steps in the evolution of equal temperament, but I was not familiar with this part of the story at all (although I have seen pictures or drawings of keyboards with multiple split black keys). And very new to me, understanding the source of the terms "bemol" and "becuadro" (the words in Spanish for "flat" and "natural" - natural as in a note that loses its alteration and goes back to its neither-flat-nor-sharp pitch). Will try to delve into this in more detail some day with more time available. Thanks!
Next to this interesting article and comments, I think mention should be made of von Helmholtz's XIX century book "On the sensations of tone". He is considered to be the father of acoustics, and derived the consonance/dissonance of the notes in the diatonic scale from first physical principles. He extracted and computed what is described as "roughness" here as the amount of "beats" between the upper partials of the notes - where beats are the slow phase oscillations caused by two vibrations of very close frequencies. But of course, he first had to study strings and pipes for 8 years, and come up with the (then) innovative concept of upper partials (harmonics). I'm a software person by trade, amateur but very dedicated musician, read this book many years ago, thoroughly enjoyed it, and I heartily recommend it today.
US culture is way more inclined towards business than European culture. American tech-enthusiasts were thinking about how to make money. Some European enthusiasts were, too, but not at all as singled-mindedly as US ones, no wonder the US owns the tech industry today. Games were a big driver for everyone on both sides, so both sides got a significant piece of the pie there (Asia was way too far back then, and arguably ahead of either).
I started learning to program in 1985, was part of a somewhat relevant demo group, attended The Assembly '94 in Helsinki, helped organize some enocounters in my country, etc...
In order to appreciate it, it is necessary to understand the difficulty of implementing something like that on an 8-bit computer from the 80s with 256 bytes of code, which is really impressive by itself. It doesn't hurt its ability to impress that the creation shows a great, coherent artistic vision, which results in an enticing, enjoyable, meaningful viewing experience - which of course is only accessible to people with the required type and amount of sensitivity.
My take is that ad revenue for TV manufacturers is next to nothing today, and it has zero impact on the cost of a TV set. But they're trying in case they can have access to a potentially huge revenue stream in the future. And my take is also that they won't do it well and they won't gain access to a revenue stream that only the likes of Google or Facebook are able to command and manage, but they will certainly annoy a huge amount of users along the way.
Only convenient option here seems to be to not give connectivity to your TV set, or not have a TV set at all.
How does it make it harder to read? Patterns and repetitions jump out of the page. Indeed, maintaining it takes time and effort, I wish the editor were smart enough, but I only see advantages with regards to reading the code.
Exactly. I format things like that in my source code. Anything else is too painful to bear. When code by other people who don't care about those things, it's hard to understand :)
I love Alan Watts too. In any case, I need to insert the necessary reference to recently passed John Conway's Free Will Theorem. I recommend every one to watch his 6-lecture long presentation on this, available on YouTube and underappreciated given the number of views, where he captivatingly describes his proof that, if we have free will, so do elementary particles. This is a purely mathematics- and physics-based proof which I understand is fully accepted by the scientific community, and while it, of course, does not provide an explanation of the underlying cause, it provides the best possible description obtained by scientific methodology so far.
I like to think that, somehow, Alan Watts and John Conway were digging the same tunnel, just starting from the two endpoints, and bound to meet at some point in the future. We just need a few more diggers of that stature (tall order, I know).