Most Adobe tools don’t have any good free alternatives even for home use.

inkscape is on a level with illustrator (maybe even better)

for drawing: try krita

if you want to pay money (much much less than for adobe): Affinity is on a level with fotoshop

if you just want to make a simple program. It still needs to run in kubernetes.

“hello OPS-team. Here is my simple program. Have fun running it on your kubernetes”

It’s at most 40 years old technolog

the 60s were 60 years ago

. But it is trained well enough to correlate left and right together

eliza could do that 60 years ago

The Ad sponsored web model is not viable forever.

a thousand times this

we’ll probably get a win 12 that is less good than win 10, but better than win 11,

I wouldn’t count on it. MS is moving away from selling desktop-stuff and towards selling cloud stuff (think azure and office356) and consulting. That’s why they changed their attitude towards linux (think wsl and c# for linux) and open-source (think github). MS wants companies to use open-source tools (preferably written in c#) and deploy them to azure with the help of MS-consultants.

Enshittifying windows is a step in that direction. For example: The more people have a MS-Account, the easier it is to sell office356. That’s why they pressure windows-user into making MS-Accounts.

MS knows that desktop is dying.

most recently I had this with energy-settings, before that with network-settings, and before that with some language settings.

I’ve not actually had this problem …(aside from [when I had this problem])

lol

the last time I had to set up a windows-system, I just said fuck-it and bought a key for 2€ from on of these shady key-sides.

There’s a lot to not like here.

the new snipping-tool is neat

yes I know if you look hard enough you can find legacy panels

In some case you have to actively looks for the legacy panel, because the new ones don’t allow to change certain settings.

However you will now have rodent problems

chicken got you covered on that front too https://www.youtube.com/watch?v=iubf1oJdQQQ

soft failures add complexity and ambiguity to your system, as it creates many paths and states you have to consider. It’s generally a good idea to keep the exception handling simple, by failing fast and hard.

here is a nice paper, that highlights some exception handling issues in complex systems

https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-yuan.pdf

============ Top 5: =============== HasThisTypePatternTriedToSneakInSomeGenericOrParameterizedTypePatternMatchingStuffAnywhereVisitor: 97
AbstractAnnotationConfigDispatcherServletInitializer: 52
AbstractInterruptibleBatchPreparedStatementSetter: 49
AbstractInterceptorDrivenBeanDefinitionDecorator: 48
GenericInterfaceDrivenDependencyInjectionAspect: 47

============ Factories: ===============
DefaultListableBeanFactory$DependencyObjectFactory
ObjectFactoryCreatingFactoryBean
SimpleBeanFactoryAwareAspectInstanceFactory
SingletonBeanFactoryLocator$BeanFactoryGroup
ConnectionFactoryUtils$ResourceFactory
DefaultListableBeanFactory$DependencyProviderFactory
ObjectFactoryCreatingFactoryBean$TargetBeanObjectFactory
JndiObjectFactoryBean$JndiObjectProxyFactory
DefaultListableBeanFactory$SerializedBeanFactoryReference
AbstractEntityManagerFactoryBean$SerializedEntityManagerFactoryBeanReference
BeanFactoryAspectInstanceFactory
SingletonBeanFactoryLocator$CountingBeanFactoryReference
TransactionAwarePersistenceManagerFactoryProxy$PersistenceManagerFactoryInvocationHandler
AbstractEntityManagerFactoryBean$ManagedEntityManagerFactoryInvocationHandler

https://gist.github.com/thom-nic/2c74ed4075569da0f80b

the fact that a system eventually becomes complex and flawed is not due to engineering failures - it is inherent in the nature of changing systems

it is not. It’s just that there will be some point, where you need significant effort to keep the systems structure up to the new demands {1}. I find the debt-metaphor is quite apt [2]: In your scenario the debt accumulates until it’s easier to start fresh. But you can also manage your debt and keep going indefinitily. But in contrast to financial debt, paying of technical debt is much less obvious. First of all it is pretty much impossible to put any kind of exact number on it. On the other hand, it’s very hard to tell what you actually should do to pay it off. (tangent: This is why experienced engineers are worth so much: (among other things) they have seen how debt evolves over time, and may see the early signs).

[1] https://tidyfirst.substack.com/p/the-openclosedopen-principle

[2] https://blog.pragmaticengineer.com/tech-debt/

also any beginner-friendly distro should be popular enough for the beginner to find it in the first place.

(big exception: if it came pre-installed on their device)

how far can you get with arch without opening the terminal or the wiki?

Yes, the arch wiki is very good and useful. The issue is, that you need the wiki in the first place. In a user-friendly distro everything would either work OOTB, or it could be done intuitively via GUI.

how far can you get in arch without opening the terminal?

“sudo MacOS” sounds like a legit way to describe “gnome+ubuntu”

KDE on steamdeck, because it came preinstalled

Gnome on work-pc, because it came preinstalled

also gnome on notebook, because the multi-workspace thing works very nice OOTB in gnome

3. Users are finally figuring out that some Linux distros are easy to use

so recommending arch linux to newbies was counter productive all along?

suprised_pikachu.bmp