551 karma · joined October 11, 2014
There isn't a reference provided for that sentence in the article, but it's something that seems true to me, from my own experience. I'd really love to see some hard research confirming or denying this.
That's simply not true, Mueller investigated Assange, but declined to prosecute due to lack of evidence that he was complicit or culpable in any crimes. He also didn't totally clear wikileaks or Assange, but noted there were 'factual uncertainties'.
I find it nauseating that Assange is being valorized as some champion of free speech/journalism, but with respect to Mueller, Assange was far from being a 'villian'.
https://www.buzzfeednews.com/article/jasonleopold/new-muelle...
It's really hard to appreciate it now because CSS (along with JS+HTML) has been extended and upgraded gradually over the years, but CSS is incredibly good for styling and formatting DOCUMENTS - which have a very specific definition, especially back in the 90's when it was first conceived. This is what is was originally designed for.
In that sense the complaints about CSS are perfectly reasonable: why are we using a document styling language for building arbitrarily sophisticated web applications when it was clearly not originally designed for that? You could say the same with HTML and JS really.
> Quit acting like CSS is some giant-ass mistake that needs fixing. A group of people who were collectively smarter than us wrote those specs. They didn’t make mistakes. Assume you are making the mistake, not them.
So what year again was the CSS standard was first published? Checks google quickly -- oh it was back in...1996. HTML was...1991. And JavaScript in...1995.
Yes, it's well known that people in the 1990's were much smarter than people in the 2020's! It's not like there's been decades of progress since then! CSS is utterly fit for purose and bereft of any flaw or defect! Absolutely nothing new needs to be invented or discovered about front-end web development in 2024! There's no point in trying to improve things!
OK, it's hilarious the author rails against things like SASS, and CSS is now being updated to incorporate many of the same features that SASS introduced:
- CSS nesting: https://www.w3.org/TR/css-nesting-1/
- Scoping (no more global): https://developer.chrome.com/docs/css-ui/at-scope
- Not to mention things like CSS variables, calc() etc.
Usually people whine about the status quo or things staying the same for too long and in response, try to improve things. This article almost seems like a big whinge about how things should stop changing and regress or go back in time? That's not happening. If people had the author's sensibilities or attitude back in the 2000's we'd never move past `float: left` for positioning or tables for multi-columnar layouts. Utterly bizarre.
Not to mention the fact that documentation is still always hand-written - which can have mistakes or typos in it, then downstream developers will have to translate that into hand-written client code, which can also have those same mistakes or bugs in it. And when the mistake is corrected, the dev needs to go back to where the correction was made in the docs, re-read and interpret the correction and then correct their client code. With API specs and code generators that entire process is automated now.
Now imagine bringing together approximately 6 different APIs into a single app, 5 have API specs while 1 doesn't. Now 80% of your time is spent on that 1 API where you have to read the docs to keep your client code up to date. Oh that 1 API vendor doesn't bother letting you know when their API is updated! So you have to F5 their website every week! This is literally my life right now.
Anyway, in this case, it was my mistake not to read until the very bottom where they had an OpenAPI yaml spec link there.
And they don't have an OpenAPI spec available to download? So they seriously expect developers to just manually write their own client code by reading and translating those example CURL commands by hand??!
Seriously it's 2024! Not having a spec to download and insepct for any API is a sign of incompetence. When tools like Postman or https://github.com/OpenAPITools/openapi-generator-cli exist and save hours of time, you can't seriously expect devs to write all this connecting code by hand anymore.
Yes it can. It's just Apple can't be bothered - most of the work to do that doesn't benefit Apple - it does benefit the Swift ecosystem and community of devs, but not Apple - the venn diagram of Apple vs the Swift dev community overlaps but doesn't completely close.
Swift came out in 2014 - Windows support for the compiler came out in 2020. That's it. They haven't bothered to upgrade the tooling support in VSCode or any other app because most VSCode users aren't Apple devs. The ball is literally in Apple's court - no one elses.
I mean, this is just absurd logic. How is the lack of Swift support on non-Apple platforms somehow up to Google or Microsoft? The burden to support more platforms is on the language developer, not the platform dev.
That is not true at all. DirextX is COM, UWP was COM based, WinRT is still COM, WinUI and the Windows App SDK is again based on COM. C++, C#, Python and Rust are all supported programming languages for the Windows App SDK thanks to - you guessed it: COM. The C++, C# and Rust language projections for it are still being constantly updated: https://github.com/microsoft/xlang
When they started Project Reunion (code name for Windows APP SDK) back in 2021, just before Windows 11's release, they decided to double-down on COM. Like hard.
https://github.com/microsoft/WindowsAppSDK/blob/main/docs/fa...
> Practically speaking, any language & runtime that can handle COM objects can support Windows App SDK
Microsoft is still actively maintaining MSVC
There's a reason they're calling it the 'FFM' API and not JNI v2. The API devs were correct in rethinking the approach to native interop.
This just proves my point; being crappy ON PURPOSE is why it's a dead end; it's very difficult to improve something that's been deliberately designed badly.
Besides that, no Java dev in their right mind is going to continue to use JNI once they upgrade to Java 22 and realise FFM exists.
That's JNI, which really was truly terrible. Java 22 introducing FFM is finally an admission that JNI was crap and a dead end.
It doesn't mention Humane or the AI Pin, there's also no brand logo in the thumbnail. Just a pic of the device itself. If you had no foreknowledge of the video or device itself, or what he was talking about, you'd have to watch at least 1 minute into the video itself to know the company and device name. The YT video title on its own can't possibly 'kill someone's nascent project' or 'cause harm' on its own.
> I find it distasteful, almost unethical, to say this when you have 18 million subscribers.
> Hard to explain why, but with great reach comes great responsibility. Potentially killing someone else’s nascent project reeks of carelessness.
> First, do no harm.
It's pretty clear they're not referring to JUST the headline/title of the YT video.
So in other words, Java is bad at scaling a basic math operation like multiplication?
> "In many ways Java is running rings around C++ performance"
The AI-space is proof positive of that being false. C++ is kicking Java's butt, squeezing literally trillions of ops per second of performance, all of this happening before the Java runtime can even startup.
The first transformer-based language model was built with PyTorth; imagine if PyTorch was a python wrapper for Java code instead of C++ code? It'd be garbage. I mean how freaking long did it take for Java to even get a basic Vector API? C++ devs have been writing SIMD optimized code for years now. And besides that, try getting a Java program to scale at tens or even hundreds or thousands of GPUs for a large language model. You'd need GPUs with literally 20-30% more RAM just to accommodate the GC.
Maybe some people do learn, and in this case it's Microsoft, who are not repeating the same thing with Blazor as they did with Silverlight.
Yeah, I'm sure he said that at the outset in 2014 when Swift launched, but in 2023, that's not where Swift ended up.
> As for C remark, our computers have long stopped being a PDP-11 clone.
There is absolutely no need for a language like Swift to be as complex and bloated as it is; browse the language spec, and about 50% could be discarded and you'd still have a very complex langauge.
The Swift team would do well to take inspiration from C and keep it simple; just stop adding new langauge features and let the existing language breathe. Full stop. Each new release keeps adding new features without any regard to how new ones negatively interact with previous ones. It's a language being designed by compiler engineers and not app developers.
And don't get me started on the bloated language parser - editing Swift projects beyond a certain size in Xcode still gets abysmally slow. All they need to do is lock down a core subset of the language and just fix bugs; make the compiler engineers speed up the parser. That's it.
> Writing low quality software that kills people, great job security even if you are at fault for peanut pay. I’ll take my non union job any day.
Boeing primarily manufactures and designs airplanes. The odds of dying while being a passenger on an airplane is about 1 in 200,000. Compare that to being a cyclist, which is 1 in 3,500. Or a pedestrian which is 1 in 485.
https://www.sbs.com.au/news/article/how-safe-is-flying-heres...
Putting your stupendously bad comparison aside, I'd say most software devs/programmers don't really need to unionise, aside from video game devs. 80+ hour work weeks, constant burn out, consistently underpaid compared to most other devs who just program boring line of business apps; they just get treated very poorly.
Also generics in the CLR isn't mandatory - you can implement a language without buying into the CLR-way of generics. For instance in C++/CLI, you can mix and match templates with CLR generics, but it's in no way mandatory. You can still write C++/CLI code using C++'s native template system: https://learn.microsoft.com/en-us/cpp/extensions/generics-an...