• 2 Posts
  • 19 Comments
Joined 5 months ago
cake
Cake day: February 19th, 2024

help-circle







  • 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.







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





  • it’s a great candidate. It was my first “real” languages (i.e. the first language, that is not php/js)

    you have a text file. then call the compiler on it, and then you have a exe file, that you can run. It does exactly what it is supposed to do without thinking about the browser, the webserver, the JVM, or some other weirdness.

    I get, that doing “good cpp” is difficult. And using all the weird languages features is difficult. But as long as you use strings, ints, ifs, fors, you should be fine. Just don’t use generics, templates, new (keep everything on the stack), multi-inheritance, complex libraries, and it’s a nice beginner language.



  • https://www.eigenmagic.com/2010/12/31/why-some-people-hate-microsoft-a-history-lesson/

    it’s worth the read, but the conclusion at the end is important

    Who cares?

    Well, everyone who uses a computer should, particularly if we consider what might have happened if Microsoft hadn’t abused their market power. When a monopolist abuses their power, customers all lose, because they don’t get to enjoy the more rapid improvements that robust competition provides. It’s one of the key reasons we think competition is a good thing.

    […] But lastly, and this is the big one for me, we might not have a monoculture of operating system on the Internet with such a poor security model.

    […] Imagine a world where Symantec didn’t exist, because viruses weren’t so easy to write and spread to all the world’s computers. Imagine a world where spam didn’t constitute 90% of all email because it wasn’t so easy to take over a PC and turn it into a botnet zombie. Imagine not having to do impromptu tech-support for family members who accidentally installed a bunch of spyware.

    […]Imagine all the time and money that has been, and continues to be, spent on fixing all of the issues that a better security model 10-15 years ago might have avoided.

    In Summary

    Microsoft have made (or bought) some excellent products, as they continue to do. There are many wise, capable, and perfectly reasonable people who work there, what with it being a big company and all. This is not a company that is an unrestrained force for evil in the world.

    However.

    Microsoft have a history of abusing market dominance in order to exclude competitors. Many of the top management running the company at the time are still there, running the company today.

    Perhaps there will be no repeat performances, but there are very good reasons for greeting rhetoric from Microsoft regarding their openness with some scepticism.

    Inflammatory headline aside, let me be clear that I don’t hate Microsoft. But I can understand why there are those who do.