Really though, what were they thinking. Why would anyone risk staying with unity after all their bad decisions, especially when they clearly have no intention to stop being dumb.
I moonlight as a small app developer. This is absolutely correct. I have a handful of legacy apps which uses Unity, and makes so little that moving them would cost more.
That said, if/when I do another project, it won’t be in Unity.
Which signals to investors that there is little to no expected growth. If you aren’t attracting new customers to grow your user base, then you only have the option to milk your existing customers to increase revenue.
That may work short term, but long term it signals a death knell for the company, since as the old customers retire or the studios close down, the new crop of game developers would have been trained on or adopted a different engine so aren’t going to switch to Unity. Eventually they just run out of customers.
edit: The following is off topic, but I’ll.leave it as a testament to my gray-beardedness. In my defense: Unity isn’t Unity anymore. Don’t get old.
I’ve been using Linux for 30 years now, and for a while I was an advocate for Ubuntu and Canonical (among others, I’m pan-distributive). Then things changed: GNOME 3, Wayland, Unity, something-sonething, Snaps… All too much.
As an advocate, I’m apt not to emerge with favorites, or to yuck others’ yums. Neverthekess, Canonical is a press beyond the pale, many days.
In the end, I don’t recommend Canonical distros. LMDE is solid, as are most of the *bian and redhat downstreams. I don’t recommend the others because I don’t know them, but more importantly I couldn’t help a friend un-bodge a bad installer on them (likewise for "BSD or Darwin).
But really, no love for Canonical. They went to some Dark Side, and I’ll have a hard time forgiving them for it.
I also thought of Unity the DE before reading the article
I understand the confusion. This doesn’t belong to a Linux community. I mean, I see the relation with FOSS but I’m sure there are FOSS communities out there. The article doesn’t even mentions Linux, just Windows and Android.
With ibm working hard to enshittify redhat even faster than newredhat themselves, we should consider avoiding them as a first-class porting and work target.
Look at OpenEL as a successor to the RH and an upstream for the other ELs once RH starts eating from that tasty “free stuff they can sell” trough. Having made bank on TheForeMan without actually making an effort to support it, they have a model they can use for everything.
I went to a game dev meetup in Seoul last year. Everyone was using Unity.
I went again last month. Half the people were using Godot.
For a bit more context, I used to work in the gaming industry. We used Unity because it was great for making money - drop in ads and tracking, you’re good to go. The Godot ecosystem isn’t as mature for that yet. However, even we were considering switching to Godot. It wasn’t worth switching for a number of reasons (besides the above mentioned ones, Godot is also “laggier” and we have some heavier games), but had we started shop yesterday, it’s safe to say we would have used Godot too.
Unity just laid off 25% of their workforce. That is not a small number. Their days are numbered.
This is basically an article promoting two Tweets (something like Toots, but on a monetized closed source for-profit platform run by a highly questionable billionaire).
No, it’s the lack of support in web APIs. Every api is based on width and height, viewport width, viewport height. Nothing allows you to find the angle of the display, rotate DOM elements to align, wrap based on diagonal boundaries etc.
Ackshually the social network you’re mentioning has changed its name so instead of “Tweets” they should be “Xeets” (like sheets por shits if you prefer).
A number of candidates will create their own forks and there will be a long Game of Thrones style war between different factions. After couple of weeks each distro will choose the fork they will make the default one and people will split into warring factions. After that we will enter a nuclear winter style period lasting couple of years during which 90% of post on Lemmy will be just shitposting the rival forks. After a decade or two of backstabbing, dirty politics and other drama new dictator will be selected and all will be back to normal.
This is the dumbest fucking thing I’ve ever heard of. I’m not buying any keyboard or laptop that has this key. There’s enough Linux-first vendors these days that it’s easy to avoid (Framework, System76, Tuxedo, etc). It’s time to be done with Lenovo and Dell.
I fully agree with you, but Framework is definitely not Linux-first. The only OS they offer preloaded on their laptops is Windows. You have to install Linux yourself if you want it.
I think they’re referring to Framework’s support for full Linux compatibility for at least Ubuntu, and making sure that the parts they use have first class Linux support and drivers and kernel integration.
This is the dumbest fucking thing I’ve ever heard of. I’m not buying any keyboard or laptop that has this key.
Which is exactly what people said about the Windows key.
Now it's all but impossible to buy a keyboard that doesn't have it. Worse, most of us use it without thinking.
Sure you can call it Super if you like, and even have a Tux key-cap on it, but there used to be a literal gap between the Alt keys and their Ctrl brethren in the lateral directions away from the space bar, and those days are long gone.
There'll be the niche users who stick with old keyboards without this new key, just like there are the die-hards who have stuck resolutely to the old IBM keyboards and the like from pre-1995, but if you want a new keyboard?
Gonna have to shell out a small fortune for a custom build or make do with that dumb new key.
(Shoutout to the Context Menu key which went as unmentioned in the above as it goes unused in day to day use, despite having been included with its Super cousin since day one.)
We have so many unused potential binds already, though. Knowing the way tech goes these days, they’ll find a way to hard-code the key to one macro and that’s it lol
Pure hyperbole “late stage capitalism”: they’ll have it wired directly into the board. At best it will cover one key chord.
Even later stage, it’ll send some proprietary data that only windows 11 can interpret. Linux users will figure it out and make use of it, then will be promptly sued out of existence for copyright infringement or something lol.
What, fuck licenses, we’re doing subscriptions here. With multiple tiers, first one just reduces the charge per activation, and the ones after that give you X “free” uses per 12 hours.
The article actually says the Copilot key will mostly be replacing Menu or Right Control on existing layouts. So if you’re already not using those (or are already re-binding them), it’s just a new keycap.
As you said, there used to be a gap there. Replacing a gap makes not that much harm and people find it useful even in Linux for keybindings. In more of an Alt kind of guy, but Super is also there for more combinations available.
The Copilot key appears to be going were the right Control or right Alt key are right now, so that’s going to be a bother for a lot of people.
It depends on how and what you’re measuring. A lot of Linux first, like system 76 and purism, do so e serious work on the firmware and boot systems of their systems. Which for some is a huge value add compared.
Same, I think I might give the System76 Darter a try when I eventually have to replace my Xps 9370. It’s bad enough that my computer comes with a windows logo on the super-key and often windows preinstalled. Shipping with a non-ANSI/ISO layout is a no-buy for me.
I don’t care as long as the placement is ok and I can map it to something useful. I’m a GNOME user so the Windows/Super key gets a lot of use. It’s nice to have. A new key that I use for all my custom shortcuts would actually be kind of nice. Who cares that the default key caps are a Windows icon and this Copilot thing? Change the key caps and they are just keys.
Isn’t archwiki one of the most comprehended wikis for Linux distros out there? If anything, the arch-wiki (to me) has often too many answers for the same problem than the other way around.
The far future: A man sits at a table, staring at a floating hologram display. He watches as an indecipherable block of alphanumeric characters wiggles and splits into two segments. He nods slowly.
He takes a breath and closes his eyes, broadcasting a message to everyone on duty that day.
“Merge the request. Tell Linus#3418 that Wayland is now the default display manager.”
Yes, but those minor traces are easy enough to remove, especially if you don't care about being "ceritified" by Google (i.e. are not planning to run the Google services).
If my device is compatible, does it automatically have access to Google Play and branding?
No. Access isn’t automatic. Google Play is a service operated by Google. Achieving compatibility is a prerequisite for obtaining access to the Google Play software and branding. After a device is qualified as an Android-compatible device, the device manufacturer should complete the contact form included in licensing Google Mobile Services to seek access to Google Play. We’ll be in contact if we can help you.
Google services are entirely missing from Android open source. The Google Play package is what contains the entirety of Google’s services.
Not sure if anyone remembers but back when cyanogenMod was the go-to, early versions had Google services included. Google sent a cease and desist notice and said it was a license violation. You cannot distribute it as part of the OS by default. The next release of cyanogenMod had it removed. Users had to flash the package if they wanted it.
Right but the topic was about google’s data harvesting and what I meant was that you can’t just grab any AOSP distribution if you want to minimize that, you need to pick one that replaces the parts that send data to google. LineageOS for example still phones google for quite a number of services.
As far as “easy to remove” goes, I think that’s kind of debatable if you want to do it in a way that’s sustainable long term considering the effort that goes into e.g. GrapheneOS or DivestOS.
Edit: here is a list of the kind of stuff you need to watch out for if you want to minimize the data sent to google
I was answering under the assumption/the context of of "Amazon wants to release an Android-based OS that doesn't contact any of Googles services".
So, when I said "easy enough to remove" that was relative to releasing any commercial OS based on AOSP, as in: this will be one of the smallest tasks involved in this whole venture.
They will need an (at least semi-automated) way to keep up with changes from upstream and still apply their own code-changes on top of that anyway and once that is set up, a small set of 10-ish 3-line patches is not a lot of effort. For an individual getting started and trying to keep that all up to do date individually it's a bit more of an effort, granted.
The list you linked is very interesting, but I suspect that much of that isn't in AOSP, my suspicion is that at most the things up to and excluding the Updater even exist in AOSP.
Six Six Six, The kernel of the beast.
Hell and fire was spawned to be released
Boards blazed and reviewed codes were praised
As they start to try, hands held to the sky
In the night, the coffee is burning hot
The commit has begun, Linus work is done
This can’t go on, I must inform the Hurd,
Can this monolith be real, or just some crazy dream?
But I feel drawn towards the GPL-2,
Seem to mesmerize, can’t avoid Tivoization!
I’m coming back, I will return
And I’ll possess your daemons and make your CPU burn
I have ring 0, I have your cores
I have the power to make my evil take its course
I still have a Rage 128 hanging around as a ‘temporary head’ for installing headless servers. Many happy nights playing Thief: The Dark Project with it, and now it’s only good for rendering a TTY at a barely acceptable resolution. And soon, not even that. Goodbye, little e-waste :-(
It’s because of the COVID vaccine mind control chips he put in everyone. If he wants to cause a storm, he just makes the entire population of Norway start flapping their arms in unison, which causes atmospheric disruption that leads to storms.
One of the specific issues from those who've worked with Wayland and is echoed here in Nate's other post that you mentioned.
Wayland has not been without its problems, it’s true. Because it was invented by shell-shocked X developers, in my opinion it went too far in the other direction.
I tend to disagree. Had say the XDG stuff been specified in protocol, implementation of handlers for some of that XDG stuff would have been required in things that honestly wouldn't have needed them. I don't think infotainment systems need a concept of copy/paste but having to write:
Is really missing the point of starting fresh, is bytes in the binary that didn't need to be there, and while my example is pretty minimal for shits and giggles IRL would have been a great way to introduce "randomness" and "breakage" for those just wanting to ignore this entire aspect.
But one of those agree to disagree. I think the level of hands off Wayland went was the correct amount. And now that we have things like wlroots even better, because if want to start there you can now start there and add what you need. XDG is XDG and if that's what you want, you can have it. But if you want your own way (because eff working nicely with GNOME and KDE, if that's your cup of tea) you've got all the rope in the world you will ever need.
I get what Nate is saying, but things like XDG are just what happened with ICCCM. And when Wayland came in super lightweight, it allowed the inevitably of XDG to have lots of room to specify. ICCCM had to contort to fit around X. I don't know, but the way I like to think about it is like unsalted butter. Yes, my potato is likely going to need salt and butter. But I like unsalted butter because then if I want a pretty light salt potato, I'm not stuck with starting from salted butter's level of salt.
I don’t think infotainment systems need a concept of copy/paste but having to write:
Having lived through the whole “phones don’t need copy and paste debate”, which fortunately got solved by now having it everywhere I’m in the camp “just stick that everywhere, just in case somebody might use it one day”
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.