426 karma · joined February 13, 2015
But this still doesn't address the problem the change is used to contain. Should defer free a variable's value as it is when defer is used or the value at the end of the scope.
And is it really such huge change. I don't find it too far removed that it becomes confusing and I appreciate the additional control over what should be freed and where. You can imagine a scenario where a variable is being reused multiple times where this kind of additional control might be useful.
They stuck when they launched. If they had only kept their business model and improved they're service they would still be doing great.
What system76 is doing could be a great opportunity to rethink a desktop for desktop users. And I understand that after so many years, users have come to expect certain things from a desktop and there's less room to innovate without alienating a huge segment of the userbase that doesn't want to relearn how to use their computer. But still it would be great to get a new idea in the space. And I would love to get an alternative to gnome and kde that isn't just a remix of the past desktops.
One side should realize they're deriding a project that's still in its infancy and it's bound to be unfinished, buggy, off-kilter, and missing features that are still more or less just rough ideas in the heads of the creators. The same can be said for any early project.
And one side needs to accept the creators were a bit overzealous and advertised features that we're really just rough ideas in their heads. And that fighting criticism with anger just makes those criticizing double down in their energy and aggressiveness.
I'm sure V will be a fine language some day. I actually like the simple style of Go's syntax. It's a breath of fresh air when you're up to your neck in "Value<double, SIUnits::m> distance;" Though I question if it actually brings anything new more than some nicer syntax. I might wait until it's closer to a v1 and make something in it for my blog.
But we're starting to reach the point where zig is becoming popular and people will hate it for that alone very soon. Because we're all really just cavemen typing on keyboards and we can't even discuss how to encode text strings without descending into tribal war.
read this for a complete answer https://www.gnu.org/software/emacs/manual/html_node/emacs/In...
The discord also seems nice and populated by people from SIGGRAPH. It's run by the Linux Foundation and seems to be an effort to create a game engine equivalent of Blender.
Overall it looks pretty decent for a first release. You can kind of see the possibility of what it could be in the future.
The fundamental issue I find with all these distribution systems is that they always seem more designed to justify a computer science degree rather than solving the problem in a user friendly way. And that applies to debs and rpms as well. All the solutions seem so over-engineered to the point that only engineers have a hope to get any kind of consistent usable experience out of it. Certainly you can try to hide all that complexity behind a nice GUI with icons and layouts, but that only works so well until something goes wrong. And then the user is stuck juggling a broken system and waiting for a reply on a support forum that may never come. That also mirrors my views on why Linux has yet to break into the mainstream desktop market.
But lets go even further, another fundamental issue. Sometimes it feels like these systems are working to justify a basic design choice of Linux that's overstayed its welcome. The idea to separate libraries and binaries was a fabulously beautiful engineering idea to fix a problem that stopped being an issue a decade ago. When your system has 32mb of storage, it makes sense, but less so when you can buy a 2tb solid state drive for $120 on Amazon. Counter to the argument in the article, storage is cheap and becoming cheaper at such a rate that continuing this philosophy will appear more odd by the day. And now we've officially come full circle and engineered it away with flatpak and appimage.
In an ideal world, these perfect systems should work beautifully. But users aren't perfect and neither are developers. That's why I now value software not by the novelty of how it solves a problem but in how few parts it can do it. For all Elon Musk's personal issues, he was letter perfect about one thing. The best system is no system. The best process is no process. For every additional step of complexity you add when solving a problem, you gain three additional problems. 1. You have to maintain it across the half-lifes of developer interests. 2. You have to teach users and developers how to use it the right way, a nearly impossible task. 3. All the systems that rely on it become more complex, duplicating problems 1 and 2 ad nauseam.
For me part of the answer was missed 12 years ago with AppImage. It works so well that I find myself breathing a sigh of relief whenever I find an application I want that uses it. That's because I know it'll just work. It's a testament to the usability of AppImages that it's still in use years later even without support from major distros. I think the linux community at large is at risk of missing something very good there. At least for user facing programs, it works wonderfully.
> The engine is extremely low cost to produce, as it is completely additively manufactured (metallic 3D printing) in only two pieces.
Btw, like others have said, it's a bit creepy looking. I didn't realize someone could make a teddy bear and somehow make it look cold and murderous but bravo. If you're going to make a teddy bear, at least make it look soft and cuddly. And give the eyes some life to them please
The internet of today hasn't changed much and is still a reflection of it's population. And if we don't like what we see it's because it highlights the worst parts of society as well as the best.
I've been doing a lot of thinking on how the internet has changed humanity since it's inception and watching our gradual change into a more connected and collectivist mentality. I think right now we're all being confronted with the imperfect creatures we are and ultimately I think it's a good thing for how we'll progress from here.
>No runtime type errors, ever. Every bit of Grain you write is thoroughly sifted for type errors, with no need for type annotations.