My smaller battery MX Tesla, after 7 years, has gone from 330km to 308km. The degradation is a lot slower than you indicate.
My smaller battery MX Tesla, after 7 years, has gone from 330km to 308km. The degradation is a lot slower than you indicate.
He’s talking about the USA, so the guard could shoot your neighbour and be suspended with pay. If he wants to be extra cautious, he could yell stop resisting after shooting him.
I am one… but I’m the only one I know at my company and socially.
The lists are quite similar with a slight reordering in the top 7 or 8. I guess both lists are a representative sample of developers… But there is one interesting difference:
IEEE: Python, Java, C++, C, JS, SQL, Go TIOBE: Python, C, C++, Java, C#, JS, VB (!), SQL
In IEEE, VB is way way down the list. Do IEEE members use VB less?
I’m always amazed that C still scores so high, but I’ve been told there is a lot of embedded work still going on.
Keep in mind that this is for « typical IEEE members », which I am pretty sure is not a great representative sample of programmers in general.
How many of you programmers out there are IEEE members?
I have one, and they are great. But wasn’t there just a scandal about a recent firmware update that applied DRM to ink?
To have library portability is a very cool feature. I hadn’t released that this was possible.
MAUI’s pretty undercooked at the moment. Editing UIs in raw XML, incomplete control set, bugs.
One day could be useful, and there are some 3rd parties providing controls… but of course this is microsoft so they will work on it for 2-3 years, and then write something new, throwing MAUI into the dustbin.
You probably did the right thing for headphones.
I’ve been looking for real data on the effectiveness of Sony’s MX5 vs Max vs others - specifically I want to see how well they do passive and ANC across the frequencies we are exposed to. And Verge have come through with this video: https://www.theverge.com/2023/8/31/23852241/we-took-six-pairs-of-headphones-and-a-dummy-head-on-the-subway
Its a good video, but its also got real data from some experts. If you are TLDW - then skip to the end for a table from the experts.
The Sony MX5 are head and shoulders above the rest (with the max second in most categories).
I know it was a sorta joke… but I had to find out if it was true.
This link: https://www.ifixit.com/Teardown/AirPods+Max+Teardown/139369 provides an awesome breakdown on the contents and lots of X-rays.
It turns out the answer is no, although both batteries are in the right ear cup, and ifixit never do figure if there is a counterweight in the other ear. There’s just a gap.
And yeah… adding that weight was a crappy move and very un-apple IMHO. Their products should stand on their own and not require gimmicks like that. Having said that, this is Beats. Analysis showed that their products cost as little as $18 to make (including parts and assembly) - talk about cheap overpriced crap. The other few hundred dollars per set is marketing, distribution and profit. Shows what celebrity endorsements can get you.
And heavy. The Max’s are quite a bit heavier than competitors.
I’m guessing you are not programming on a Mac then :-).
I’m usually a little suspicious of a new fancy language - because the language is only a part of the equation. Does it have good tooling and does it have awesome libraries?
I had a preconception that Rust is strong as a language (formally well structured, low shoot-yourself-in-the-foot potential, consistent, predictable) and that the tooling seemed strong (debuggers, editors, code completion, help, test frameworks), but I’ve always thought that it would lag with libraries. I mean compared to something like Python (« Batteries included ») or java, surely it is not yet compatible, right?.
So I chose a few of the less main-stream libraries that I use regularly… and Lo and behold! They exist for Rust, including Couchbase, SQLite, ECDH, DiffMatch. I can’t vouch for the completeness of those libs, but the fact that everything I looked for existed… that’s impressive.
Cache clearing has been mentioned as a way to fix issues, but it didn’t work for me. I agree with your comment about the value in having a second IDE though.
No. I’m on a Mac, and VS is Mac/Windows only. (Well… windows only from next year).
After I saw your note, I had a quick catchup on that project.
It looks awesome, with the promise of mobile and desktop, and the ability to make apps that can be uploaded to the AppStore. Plus its Dart which is a pretty well structured language. Its ticking a lot of boxes…
Then I ran « wc -l » on my support libraries (i.e. not UI code) - 64k LoC that would need to be rewritten in dart. But then I noticed Flutnet. its probably an abomination linking the two… but it could be promising.
Thanks for the pointer.
Thanks. I’m very out of date with it.
I’ve had a few years experience in both C++ and C#. The learning curve is a lot steeper for C++ with many more opportunities to shoot yourself in the foot or create horrible hidden memory leaks. It sounds like the person making the recommendation is talking out of their arse.
If you have any experience in Java or any OO language, then the transition to C# is not so large. The language itself is not difficult - it will probably a couple of weeks to be comfortable. Its the frameworks and libraries that takes time, and there are a lot.
Here’s my view… it takes 10 or more years (IMHO) for a sharp person to become a senior developer. It takes a few weeks to learn a language. If I have to choose for a big project, I prefer to focus on choosing the right person, rather than just focusing on the language, because a good senior will just learn whatever they need at the start. They will also bring their years of experience in good design, methodologies, communication, mentoring, testing etc to the party.
I take back this comment partially. As 2023.1 (which I have), rider failed to support MAUI. As at 2023.2, they say they have preview support available. I’ve downloaded, and am giving it a try.
I learned the hard way about the beauty of backups and the 3, 2, 1 rule. And snapshots are the GOAT.
Even large and (supposedly) sophisticated teams can make this mistake, so dont feel bad. It’s all part of learning and growth. You have learned the lesson in a very real and visceral way - it will stick with you forever.
Example - a very large customer running our product across multiple servers, talking back to a large central (and shared) DB server. DB server shat itself. They called us up to see if we had any logs that could be used to reconstruct our part of their database server, because it turned out they had no backups. Had to say no.