I used to record concerts I went to with a minidisc player and a small battery powered mic.. I have Beck, Radiohead, Dj Shadow, Kid koala, Q-bert.
Defo fun to listen back to, especially the bullshit my friends and I were saying.
Also there was a shop in Temple Bar Dublin that seemed to specialise in selling bootlegs. They were really expensive, but really good, clearly taken from the sound desk.
I'm a very experienced Unity C# programmer, and I certainly don't equate "good" with using all the new fancy features of a language.
Fancy features are less maintainable imo. Less programmers will know about them and they're less likely to have equivalents in other languages.
Making something more exotic / confusing / hard to parse is defo not worth saving a few lines of code.. I'd much rather see a longer function using absolute bog standard elements of the language (and thus being clear, easy to comprehend for everyone, easy to modify at any point) rather than a super short, super "elegant", super "clever" solution.
Languages that seem to indefinitely grow more features over time (like c++, c#, rust, etc) evitably become bucketed by epochs unless the consuming application code also operate across the same time scales. Feature deprecations tend to go hand in hand with newer features, leaving you with basically "multiple sublanguages" in a supposed single language, exacerbating fragmentation of the community. I don't want to have the mental load of contextually understanding "which" sublanguages I need to care about depending on the year a consuming application was written. This is why I tend not to reach for new fangled features and stay with the core runtime stuff in evergreen langs.
I don't know... I feel like a lot of these features do increase developer intent without breaking muscle memory. Properties are got and set like fields. Record types feel like classes with restrictions so the linter can warn you about broken assumptions. etc etc.
Others increase readability. A LINQ statement is a lot easier to parse than a long block inside a foreach.
New doesn't mean good but a lot of these are new and good.
I disagree about LINQ. You can easily do the same job in a little function with only stuff people learn in week 1 of programming, just for and if else and arrays. It's very clear precisely what's happening in this case, and its easy to alter. (Everyone is gonna know that stuff, not everyone is gonna be using LINQ regularly enough to understand it completely)
LINQ on the other hand is like another language entirely, awkwardly squished into your C#, reminds me of SQL code inside a big string inside another language's code. It's also not clear what it's actually doing which can be death for performance in games as LINQ usually allocates shittonnes of new stuff. (I'm certainly not advocating for premature optimisation, but I defo am advocating for knowing precisely what you are writing)
The benefit of LINQ is that its a bit faster to write compared to a little function, but length-of-time-it-takes-to-actually-write-code is very rarely an important constraint in my experience.
"It’s not realistic or feasible to have the US government generate a fiber optic connectivity for the entirety of every household in the United States. In fact, the free market was the only realistic possible to deliver this."
Why? Other countries with similar population densities have done it. A bigger country should have an advantage due to economies of scale.
I think he means it's not economic viable to the companies, however as you can see the Swiss model was defined by politics.
Even though, I agree with you it's possible, in my city the internet only got better when a monopoly was broken, and a state company decide to work in a new infrastructure, all FTTH, now I pay less than 100BRL for 300/150Mbps with that price 10 years ago it was only possible ADSL connections (25Mbps).
Now every major provider do have FTTH infra with great prices.
Saturn 5 had a flawless record. The leftover space shuttle parts which SLS is cobbled together from, not so much. SRBs are inherently dangerous, theyre designed to quickly launch nukes from silos, not people. And Orion is just a typical modern Boeing project. So far its fallen at every hurdle right?
Saturn 5 came close to catastrophic failure at least once. It had partial failures. Its sort of perfect record is mostly down to luck and not launching very many times.
Of course, six decades later, we should be able to do a lot better.
Yeah, I thought it was Starliner on top. I dont know anything about Orion then.
SLS is very crappy and disappointing, its using shitty old space shuttle tech, + its ridiculously expensive in terms of payload to orbit, but it will probably work.
I didnt know, cus I just dont give a shit about this stupid project.
Just curious has anyone ever contacted customer support in the past decade and not gotten the message saying their call volume is high atm and thus the wait will be "longer than average"?
Eg. https://youtu.be/ucRTW4rgrbU?si=dfRIy76BM8ntNQph
reply