That would be such a killer feature. And it could find other friends in the area and that are also free. Not like Meta doesn't have some kind of model for all that data already probably.
Weird software X diabetes story. CFO at my small startup had type 2. We only had sugar free sodas and water bottles and, oddly, Capri Suns at my 15 person startup. I distinctly remember wracking my brain working on some code for long day and my brain was like "give me sugar!". I didn't realize that attempting to feed it many (sugar-free) sodas, it wasn't getting what it wanted. It needed the glucose. I began surreptitiously drinking Capri Suns. My CFO sees me chugging aforementioned childrens' drink and informs me those are his emergency sugar drinks and please don't accidentally kill him if he ODs on insulin. Never learned so much biology while writing software in my life.
It's one thing to reduce dependency and another to have reduced consistency. If you have 10 web routes and 1 behaves differently, it doesn't matter if the code is cross coupled or not, it matters if it behaves similarly. Does it return the same status codes on error? Does it always return JSON with error messages inside? Do you auth the same way? The implementation can be wholly separate but end users will notice because logic on their side now has to special-case your 11th endpoint because you returned HTTP 20x instead of 40x on error. Or when you realize that you want to refactor the code to DRY it (Don't Repeat Yourself), now you can't reduce all the duplication because you have bespoke parts.
It only supports up to 800x600 resolution? For real? I know people like low res games and this is targeting old hardware but that is surprisingly low to me given the touting of how optimized this is.
Please elaborate what programming language you think isn't a fad and isn't a playpen and why. Restrictions on languages IMHO clearly narrow what you have to think about other code doing. Whether it's marking a field "const" in C++ or having the borrow checker in Rust or having private fields in Java or immutability in Clojure, all those things make it easier to know what a large system of code /cannot/ do, and that makes it easier to maintain. That has nothing to do with people other than it might be you fighting years of code that you wrote yourself.
I'm optimizing for a large, complex corporate projects, not beginners on toy projects. And I would also add that if you search for "how do you do X in Y language", you'll probably find every combination of a lot of languages so I hardly think that is grounds to dismiss Clojure. More and more languages seem to be embracing immutability and static functions are everywhere. The two are just utilized well and believe me, if you need to refactor something then you are so much more at liberty which is certainly a high bar IMHO.
Totally agree. I think the biggest and most important things a language designer chooses is what to disallow. For instance, private/package/public etc is one small example of an imposed restriction which makes it easier to reason about changing a large project because if e.g. something is private then you know it's okay and probably easy to refactor. The self-imposed restrictions save you mental effort later. I also love lisps but am a Clojure fan. This is because in Clojure, 90+% of the code is static functions operating on immutable data. That makes it extremely easy to reason about in the large. Those two restrictions are big and impose a lot of structure, but man I can tear around the codebase with a machete because there are so many things that code /can't do/. Also, testing is boneheaded simple because everything is just parameters in to those static functions and assert on the values coming out. I don't have to do some arduous object construction with all these factories if I need to mock anything, I can use "with-redefs" to statically swap function definitions too, which is clean and very easy to reason about. Choosing the things you mr language disallows is one of the most important things you can do to reduce cognitive load.
You sound very defeatist about fighting bureaucracy. If you work at an org with too much management, you can slowly push to move it in the direction you hope for or leave. If you keep ending up at places that seem impossible to change, perhaps you should ask more questions about this during the interview. I've worked at many small companies where there wasn't crazy bureaucracy because that's definitely what I preferred. I also currently work at a megacorp and yes there is difficulty, but being consistent and persuasive has lead to many things slowly heading in the right direction. Things take time. You have to realize why people have made things some way and then find convincing arguments to make things better. Sometimes places do just suck so don't stick around. But being hopeless doesn't seem helpful.
I just wish there were a higher resolution image than the one linked in that website. The original photos of M87 are so stunning and have such a cool story where they split the research group into two teams and they both came to the same conclusion about the discovery of the black hole. The photos that go along with the original discovery were my wallpaper forever because it just looks so awesome.
Did you know that something like 80% of the websites you visit are tracked by a handful of companies which are all effectively sharing that with many thousands of ad and data broker companies which can easily narrow you down? It's not tinfoil hat land to knkw that nearly every site you visit has cross-site tracking.
I seriously pisses me off that they make the font so small on the opt-out signage and you get told by a uniform to stare at the camera like you have no choice. Everything you don't fight for ends up getting taken.
There are probably only so many obvious metrics from which to pick and you wouldn't have to game them all, just pick the easiest ones and keep grinding. Fraudsters are usually motivated and not that dumb.
Also, for Java, Virtual Threads are a very new feature (Java 21 IIRC or somewhere around there). OS threads have been around for decades. As a heavy JVM user it would have been nice to actually see those both broken out to compare as well!
Almost certainly only the install. Uv is basically a pip tool substitute with a few other bells and whistles too but shouldn't affect run time whatsoever.
That's assuming independence. I'm not ruling out sabotage but the world is often not fully independent. A storm or an anchor both may affect multiple cables if they're in generally the same area which would definitely make the probability far more likely than those stated. (edit typo)
Who said you had to junp to single celled organisms first? One of the oldest displays at a science museum I remember was very simple. It was basically a rubber sheet attached to the top of a spinning pole resmebling a folded umbrella without the spines. There was a adjustable knob you could play with to adjust the speed that it spun. It would start from zero. Versus interestingly to me, the exhibit demonstrated that at certain speeds the dangling edge of the rubber sheet would form nice sine waves at certain speeds. It might be chaotic at first but eventually, given just the right amount of energy to spin, the wave would appear. If you sped it up or slowed it down, sometimes the wave would collapse, but if you hit another natural frequency, it would eventually snap into a larger or smaller amplitude with a greater or lesser amplitude. My take away was that if there is enough energy and repetition to almost anything, eventually patterns will arise. And if you let them do that long enough, then even in imperfect environments, relatively stable outcomes would occur. Much like life in my opinion. Have enough chemicals and energy thrashing around long enough in a cycle, and enough adverse selection against all those structures, eventually some structures will emerge and self-reinforce. Doesn't gotta start with cells, just molecules.
This is a very computer science and not scientific response, but I look at the Game of Life, and it makes me realize that little patterns naturally form everywhere. Biology is just a little pattern that wants to replicate and survive and that doesn't have to mean intelligently.
What if you represented arrays as recursively nested triples like '(1 2 3 4 5) as [[1 null 2] 3 [4 null 5]]. Then you could parch the tree of triples much more succinctly. You might have to disallow nested arrays but this would as bad a restriction as disallowing nulls as map values. You could append and delete array indexes better. Or maybe make it an 8-way tree like Clojure does for its vector representation to condense the patch further.
"In some ways, they are the holy grail of concurrent data structures. On the other hand, a concurrent hash table is an inelegant blob of shared mutable data, often a marker of a poorly architectured program."
I find the last bit particularly objectionable. If you're in some language slanging objects around all day, then sticking a untyped, bespoke substitute for an object probably isn't the right move. But on the long path down my programming career, I recognize objects make so many things harder and more confusing than necessary. I definitely prescribe to Rich Hickey saying I would rather have 1 data structure and 100 functions that operate on it far easier to work with and understand than 10 data structure and 10 functions. Clojure absolutely is a joy to work with and reason about, and it only gets better the faster you get out of typed object land. Hashmaps are the purest abstraction over an associative data structure, and I will take one over a pile of classes with brittle, snowflake interfaces any day.
While noble, the immediate strategy with that is that prototypes can be overwhelming expensive in time and money to produce. Patents are supposed to protect inventors, but if that's the bar then right out the gate you are favoring the corporate behemoths who have the resources and can then just snatch the idea and weasle out the not-so-resource laden inventor. This is the type of thing where there seems like there should be easy solutions to the problems but a little nuance reveals that these things are very lucrative and some level of corporate apparatus will find a way to abuse the system and reap potentially hefty winning at the expense of the actual people coming up with stuff.
One of the rules of HN is to assume good intent. People do and say the right thing often even when it's antithetical to their source of income. If there is a substantive way to otherwise then say it, don't immediately write-off people's opinions, especially people in their fields because of a possibility of bias.
I think the same could be said software engineers. I don't engage with the general public about writing people's next brilliant idea because it's a hige waste of my time when I could be making FAANG bucks talking to people who know that I'm worth it. While I will alwatry to explain to my mom how the internet works etc, it's not economically justifiable to engage laymen tonsolve their probno matter how altruistic it may seem. I still have to pay the bills. How are lawyers any different?
Not having data is not the equivalent of only talking in opinions. I will tell you rhat gathering data can and usually is tedious in many things. If I have to measure every single thing to make any argument, I'm quitting. Looking and thinking in data isn't a bad idea, but if it's just used as a crutch in an argument, then what I think the OP is arguing is that their manager is using it as a tool to make decisions but likely only the decisions they disagree with. As an engineer, I know many times that changes I make are going to work better, sans some fancy chart. If they're not, I think they'll show up on a graph one way or another and I think it's also healthy to be told my assumptions are wrong sometimes and I will happily revert my code. But I've never seen any org make purely data driven decisions as it is truly difficult to do, and whoever is saying things like that probably is selectively using that argument to get their way.
Your comment is a bit snarky and I understand what you're saying but my understanding was that everyone thought Moore's Law was over when the computers stopped getting 2x faster every 18 months but that's not what Moore said. He said the transistor count would double amd it just so happened that that meant computers got a lot faster too because they benefited from all the xtra transistors. But GPUs do still get faster with more transistors because of the embarrassingly parallel nature of many matrix operations. So doubling the transistor count could still effectively significantly improve the speed and reduce time of AI training which is dominated by matrix math. Am I wrong? Did the transistor count doubling also slow down?
I wish there was a well-supported Lisp in Rust, not just the macros. I wonder how much memory safety you would retain or lose being based in Rust. Is it even possible to leverage the borrow checker any any sane way?
I agree, when you say you're going to do something then obviously you should also do what you say and say what you do. But my guess is even just saying I learned you don't feel heard about xyz and I will try to pay more attention to you your concerns when you're talking about xyz shouldn't be hard to commit to if you care at all about whomever you're talking to. Hopefully they are a bit disarmed and realize you're trying. I don't think this is a silver bullet, and I think the article makes that point at least a few times. The point is to try and stabilize and correct the vibe if it isn't really justified. If you are going into a warzone then you probably need different advice, hopefully this isn't the norm though and you aren't a hostage negotiator or something.