why not have a single global timezone and people change their local numbers.

e.g. if you life in hawaii you stand up at 11pm and if people in russia work until 8am.

how does it compare to yt-dlp?

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”

is this a jojo reference?

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 goldberg-steamcrack supports multiplayer. https://gitlab.com/Mr_Goldberg/goldberg_emulator

I only tested it in lan, and it works great. Not sure if it works online, too. You may need hamachi.

And of course: online multiplayer with randos is probably not worth it, as others have pointed out. On one hands it’s probably a bitch to set up. On the other cheating is probably rampant.

But only temporarily

but is it?

I thought the temporal improvement would be for everyone who already used the high way (because they will get to their destination a little bit faster). And for the few extra people, who start to use the highway but didn’t use it before, the improvment will stay.

When you add a new lane to a road, people think that the traffic will be easier there, so they take that route instead of their normal one

so for these people the new lane will create marginal improvement, right?

The Ad sponsored web model is not viable forever.

a thousand times this

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.

related: Roko’s basilisk

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

how many state-border did you cross there?

Yeah, but you aren’t driving that fast in Germany

*confused autobahn noises*

============ 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/

why not?