I don't know why Blade was decided on, but it was started by Kvark who worked on WGPU for Mozilla for some time. I assumed it would be a good library on that basis.
I harbor similar sentiments, but I understand why OpenAI, Anthropic, Zed, etc begin with a macOS version. They're able to target a platform which is a known quantity and a good jumping off point to Linux.
I'm writing software for Linux myself and I know that you run into weird edge case windowing / graphical bugs based on environment. People are reasonably running either x11 or wayland (ecosystem is still in flux in transition) against environments like Gnome, KDE, Sway, Niri, xfce, Cinnamon, labwc, hyprland, mate, budgie, lxqt, cosmic... not to mention the different packaging ecosystem.
I don't blame companies, it seems more sane to begin with a limited scope of macOS.
I would have a very hard time accepting it to be true. They don't even strongly make the claim that it is true, they are correlating areas of the brain associated with memory as growing larger, and they are associating a larger brain area with better cognition, but later in the article indicate that there are some areas of the brain which are associated with memory which actually shrink.
I think we should question research which is overwhelmingly against our common experience of life. My memory is absolutely shot when I am consuming weed regularly. It's not particularly subtle, it is noticeably worse. I suppose there is room for a situation in which it is worse while I am heavily using, but if I were to cease maybe it will rebound and settle at a point which is better than it would have been had I not consumed any cannabis... but I don't see any reason to believe this.
The reason Wayland progress is slow is not technical. We have a coordination problem, people have differing priorities and views on what should be allowed.
There are people opposed to things like a allowing windows to specify their own bounds, and unless all the stakeholders agree to implement such protocols in their respective projects, the ecosystem will remain fragmented. Multiply this against every feature that people want.
This is from 2019, prior to the finalization of modules in the standard. I'd be interested in how many of these issues were unaddressed in the final version shipped.
There isn't much of a final version shipped. It's pretty well understood that modules are underspecified and their implementation across MSVC, clang, and GCC is mostly just ad-hoc based on an informal understanding among the people involved in their implementation. Even ignoring the usual complexity and ambiguity of the C++ standard, modules are on a whole different level in terms of lacking a suitable formal specification that could be used to come close to independently implementing the feature.
And this is ignoring the fact that none of GCC, clang, or MSVC have a remotely good implementation of modules that would be worth using for anything outside of a hobby project.
I agree with the other commenter who said modules are a failure of a feature, the only question left is whether the standards committee will learn from this mistake and refrain from ever standardizing a feature without a solid proof of concept and tangible use cases.
I did prior to 2017. I realized the committee was 75% politics and people with a lot of time and devotion pushing their pet projects, and about 25% about addressing actual issues faced by professional engineers and decided it was no longer worth the time and effort and money.
The committee is full of very smart and talented people, no dispute about that, but it's also very silo'd where people just work on one particular niche or another based on their personal interests, and then they trade support with each other. In discussions it's almost never the case that features are added with any consideration towards the broader C++ audience.
You learned nothing because the extent of your knowledge tends to be rather superficial when it comes to C++.
Office does not use C++ modules, what Office did was make use of a non-standard MSVC feature [1] which reinterprets #include preprocessor directives as header units. Absolutely no changes to source code is needed to make use of this compiler feature.
This is not the same as using C++20 modules which would require an absolutely astronomical amount of effort to do.
In the future, read more than just the headline of a blog post if you wish to actually understand a topic well enough to converse in it.
I think if you were to poll people, a significant portion would be repulsed by this catgirl aesthetic, or (though this isn't the case for Anubis) the cliche inappropriately dressed inappropriately young anime characters dawned as mascots in an ever increasing number of projects. People can do whatever they want with their projects, but I feel like the people who like this crap perhaps don't understand how repulsive it is to a large number of people. Personally it creeps me out.
I'm not repulsed by it but I do wish the people that forced this stuff into their software/hardware realized how juvenile it makes their product look. There's a decent cheap Chinese pair of Bluetooth earbuds on Amazon that's been very popular among audiophiles but the feedback sounds are an anime girl making noises and there's no way to turn it off so I lost interest in purchasing them.
well for the bluetooth headphones i dont think you were the target demographic.
but open source generally isnt treated as a product. its just a bunch of volunteers having fun writing code. its natural that they will include their other interests in it in some way because it makes working on a project more fun. first impressions matter a lot, but i dont think foss projects should optimize for that instead of having fun.
> (though this isn't the case for Anubis) the cliche inappropriately dressed inappropriately young anime characters dawned as mascots in an ever increasing number of projects
I think the fact that people bring up things that the Anubis mascot isn't when talking about Anubis is more telling of their own harmful (and potentially racist) biases against Japanese-styled media than it is about the idea of having anime-styled mascots for free software projects.
It sounds like something you might benefit from talking to a therapist. It's not normal to have such a strong reaction. I hope you can get the help you need!
This is intentional. The version with the fun art that expresses the creator's individuality is free and open source, but they sell a paid version with bland, corporate-friendly art that also supports custom art and CSS. This makes the project sustainable to work on without having to worry about corporations that care about professionalism/how people like you think/etc not supporting the project financially.
I don't think Helix can currently match the C++ experience you get with VS Code.
* Debugging is rough. There's experimental DAP support, but it isn't ready to be used. I was able to set breakpoints and step through the code, but the UI for exploring variables / state while paused felt missing or was unintuitive enough that I couldn't figure it out. I use CLion for debugging.
* Goto definition works with clangd as long as your CMake setup outputs compile_commands.json, which you already do.
* Renaming symbols (variables / functions) via clangd works fine.
* Intellisense is decent, but I had to tweak clangd settings. By default, it would stop returning results after scanning a certain number of symbols, so some valid functions just didn't show up. I was using Helix for a few days before realizing this problem, it isn't obvious that you are getting an artificially constrained filtered view of your symbols via default clangd. Maybe this is a distro packaging issue though?
* The order of intellisense completions is not great. CLion is smart about surfacing relevant suggestions first. In Helix + clangd, I often get obscure symbols that obviously have nothing to do with my project or context. It's not the worst thing, but it is mildly annoying and noticeable.
* "go to error" doesn't surface errors in files that aren't open. In Helix, space D brings up workspace diagnostics, but it only shows errors for compilation units already open. This appears to be a clangd issue, as space D in other languages will show all project errors. CLion does not suffer from this problem.
* I think you can get LLM suggestions via an LSP, but I've not tried personally. Assuming it's true that you can get LLM suggestions, it's not clear to me that you can run two LSP's on the same file, so it might be a choice between clangd and an LLM LSP? Not sure.
* No integrated build support. You'll probably end up building from a terminal. I use Wezterm with a custom lua script that is invoked on a hotkey. I put a lot of thought into the build UX, and what I've done is both extremely hacky and still not good enough.
Helix is not flexible, it's uncompromising. I like it, but I think it's hard to beat CLion or vscode for C++ development.
I'd say right now, if you have a good setup already, stick with what you have.
Well, if the recent drop in views was due to adblockers, we now have some data about what percent of viewers block ads. There would have to be an effort to collect this data, and the view discrepncy is probably going to differ by genre of video (eg, tech youtubers probably experienced a greater dip), but this should roughly tell us how much is lost to adblockers.
Creators have stated that while their viewcount is down their ad revenue is not - but a lower viewcount still presumably hurts youtubers for in video sponsorships, and if some genres of video have a higher portion of users with blockers, that probably hurts that entire genre in the algorithm. It sounds like viewcounts are returning back to normal though.
Well, I meant how much is lost financially. Ah, unless you mean that people would watch less videos if they were subjected to ads, which is a great point I didn't consider. You're right, you can't just linearly extrapolate as I suggested due to that.
It is frustrating. Rolling back forever chemical regulations is analogous to reintroducing leaded gasoline. Should we be expected to debate and weigh the pros and cons of leaded gasoline? Some things require nuance, but some things are clearly and unambiguously bad. PFAS have well known health risks, they're persistent, bio-accumulative, and linked to cancers and endocrine disruption. We should err on the side of caution. An angry reaction against this is justified. It's insanity.
That’s the argument—yes. Consumers are supposed to educate themselves about all the industries in their backyard before buying a house to make sure that none of them have ever dumped PFAS in the last 100 years. And also they need to move to a place where it doesn’t rain, because PFAS is also in the water cycle. If nobody does that then the free market has spoken.
