h4x0r12345
h4x0r12345 on Hacker News
> that's called "dodging the question"
That is an immature non-intellectual response. I am done with this thread. Have a good one.
Are you typing on a Chinese computer or a US computer? If you were using a computer 25 years ago, what about then? Made in USA or China?
And how's your infrastructure looking these days? Last time I was at LAX 10 years ago it looked worse than a third world country airport
This is exactly what I mean by "disingenuous bullshit". CPI is a distorted corrupt measure of price levels. Money supply cuts through that.
Correct. Some would argue that CPI is specifically engineered to mislead.
The M1 significantly outperforms Ryzen when measured by performance/watt and single-core performance
What you're describing is dysfunctional manipulative unprofessional infantile nonsense - sometimes also known as "Corporate Cringe".
Go to YouTube and search for "josh fluke corporate cringe". His channel is becoming more popular as he exposes this crap.
Your wording is not precise
> In order to even get the IDE working with a project you need to configure it to work.
Meaning you already have a Maven/SBT/Gradle project and need to get the IDE to work with it.
No that's not how it works. IDEA has its own project files (*.iml, .idea), separate from Maven. We are talking about IDE projects which are separate from Maven.
From the perspective of a business owner, an employee is someone paid to do an actual job. They either do the job they are being paid to do, or they're fired. They're not part of the business owners perceived extended family unless the business owner is mentally ill. Employing someone to be a pseudo-family member is psychotic and probably illegal.
Exactly. The youngsters like to show off their L337 hacky editor configurations. The rest of us are just getting actual work done in IntelliJ or Visual Studio.
> I don't know if people just aren't aware, but vi and emacs have been doing this since at least the 90s. This isn't some fancy feature that requires an IDE. Recently the support has improved even more through LSP.
We know about them. When you start adding these scripts to vi and Emacs they're no longer in the realm of plain text editors. You can add a bunch of hacks to turn vi or Emacs into a poor mans IDE.
The minimum targeted device is sometimes not even capable of running the development environment. Doom was developed on $10k NeXT workstations. Good luck trying to develop Doom on a 386.
If you have a Maven project, IntelliJ will open it and configure itself automatically. The IDE user doesn't need to know anything about Maven build configurations. It just works.
Generics use the type system to make the compiler check the code for you. It makes the code easier to understand, more correct, and concise if you use them as they were intended. It avoids tedious and error prone duplication of logic. Create ONE efficient debugged implementation and reuse it as much as possible. The crappy workarounds for generics introduce their own complications and issues.
But I know what you mean. I've worked on Scala code for years and seen less mature developers over-engineer things and get way too clever with the type system. Scala is a really practical and powerful industrial language that requires some maturity to use the abstractions sparingly. It's only good for the top 5% of developers.
However, Go doesn't have such a powerful type system. It looks like the Go designers implemented relatively simple generics. You have to draw the line somewhere. If simple Go generics are too confusing and complicated then that developer should probably find another job, as generics are a basic concept in programming. The Go designers are pragmatic people, and they've decided that relatively simple generics will make things easier in mainstream commercial codebases.
No, it's relative. For the top 5% - 10% of developers, generics are a useful tool for doing their job efficiently. For the bottom 50% of developers, generics are complex and confusing, and only provides more footguns.
Generics (and other abstractions) are not the root cause. Go was a pragmatic defence against mediocre developers. The majority of developers are mediocre by definition, and will abuse _any_ abstractions to create Rube Goldberg contraptions and monstrosities.
It's well known that they've already tried to insert back doors many times. On the other side is a huge amount of resources auditing and reviewing the kernel. Many reviewers, auditors, security analysts.
Back doors in the Linux kernel source code? No.
Back doors in GNU/Linux distribution repositories? Maybe.
These are very childish and silly arguments. The letters have strong conventions in mathematics and definitely make sense when the functions are generic. It's like impulsively criticising Haskell or any other formal language for looking stupid and "worst possible" when you haven't put any effort whatsoever into learning it.
https://t2linux.orgIt runs well if you have the time, patience and expertise. There's no fundamental technical barriers. It's purely a matter of enough development resources being committed to the project. I think Apples recent moves would motivate more developers to work on it.
Donate a few dollars monthly to
https://asahilinux.org on Patreon. We'll get Linux running smoothly on the M1 within a year or so.