ReflectedImage

I didn't mention anything? But I'll answer your question anyway.

Be it software, artwork, essays, graphic design or movie clips. There is a market for shipping cheap junk.

Well assuming it's successful, there will be a large number of companies who's value will be reassessed as the token cost to replicate and run the business.

Multi-million dollar companies will be reduced into multi thousand dollar companies.

The CEOs will be replaced with teenagers in garages with their parent's credit cards.

If it stalls, then China will undercut the whole AI market with cheap electricity and crash the US stock market.

So what exactly is the win scenario here?

Apple only dominate the US mobile phone market

Probably a con job. The AI companies don't think they will be able to significantly improve their models in the next year or so, so they are stalling with government regulations whilst taking in investor money.

"From the perspective of the Iranian state" Well you say that but they have got a non-nuclear nuke equivalent in the form of kamikaze drones.

There is a designated third party Pakistan and they say Lebanon is part of the ceasefire.

Oh no, I live in a flat in a converted commercial building.

They have been going wild in the UK converting office space to residential.

The Spanish tankers aren't going through because there aren't any Spanish tankers that operate in that region.

Spain has permission from Iran to send through tankers if it indeed had some.

So going forward all countries will be providing citizens of other countries free access to the internet whilst censoring their own citizens?

Static typing and duck typing both date back to the 1950s. You may have heard of Lisp.

The last new significant thing invented in programming was OOP in the 1990s.

Everything else is just ancient, OOP was about bringing the benefits of micro-services to single computer environments. Yes, you read that right

The new ECS system for 3d games was used by the first computer drawing program Sketchpad in 1963.

Programming is mostly just recycling ideas around and around.

The issue is that duck typing with a minimal set of types was the great idea of ABC, which is the language Guido cloned to make Python

instagram @dhsgov DS8Tx3XCRLQ

Well given that the US DHS is posting on social media that it intends to get rid of all 100 million non-white Americans. What exactly did you expect?

If you are a good software developer in India then you move abroad. It's not that India doesn't make great software developers, it's just they don't tend to stick around.

Well either $100,000 per person or an large one time direct donation to Trump to be legally exempted from that charge.

MAGA at its core is a rejection of the lower classes having wealth.

Replacement? They haven't overthrown the Venezuela government just captured it's figure head.

Well I don't think anyone would pay for the COBOL to Java conversion software.

Since it's no longer New Years Eve, I'm a bit more sober :p

Programming language to programming language conversions seems to be one of the things LLMs are actually good at. Whether they can actually do it or not is an open question.

CEOs will mandate security so the CSOs will mandate Rust over C/C++ and so Rust will slowly take over C++ in next 20 years. Can't see anything in C++'s defense other than it's legacy. The drawback of sticking every feature from every language into your language is that it becomes a massive security hazard.

huh? I'm currently at $1500 Monthly Recurring Revenue, so I'm currently between seeing if I can increase that or if need to get a job. I'll find out in a couple of months.

Well it's in Windows, Linux and Mac OS kernels. So you moving into Retro computing?

Yep, not a single line left. Retired quicker than COBOL. Won't even be any maintenance jobs for legacy systems left.

Have you heard of Microsoft's C++ elimination plan? They are building an LLM based transpiler that automatically turns all C++ code into Rust. In a couple of years, there won't be a single line of C++ left... Isn't that wonderful?

The military isn't going to allow C++ anymore due to it being a massive security hazard. You can't get away with buffer overflows, use after frees, data races, etc. forever.

Due to an evil entity called the military industrial complex, you are going to be using Rust in the future.

If JITs hadn't been invented you would be completely right but JITs have been invented.

There are deeper optimizations that JITs can do such as knowing at runtime that the value of a variable is always 2 that typing information simply can't express.

Duck typed Python is optimal for development speeds, the only thing that matters in startup environments. It has it's niche.

You aren't gradually improving, you are gradually deteriorating the codebase to make it look more familar to you.

The problem is there are a lot of developers who have only coded with static typing and have no idea about the terrible drawbacks of static typing.

They don't understand what static typing does to code verbosity and development times.

Take Turborepo going from Go's typing light system (designed to emulate duck typing) to Rust's heavy typing system (true static typing). Originally the code was 20,000 lines and was coded by 1 developer in 3 months. When moved into the typing style you like so much, the same code is now 80,000 lines and was coded by a team of developers in 14 months.

Absolutely not. Duck type based development results in working code out of the door 3x faster than static type based development. It always has since ancient times.

If performance wasn't an issue, then the static type based developers would all be fired. Either directly or by the businesses who relied on them getting driven into bankruptcy by their competitors. You would still get some niche jobs in it where they like to do formal verification of the code.

Your problem is just that your development skills from static type based development don't transfer to duck type based development. Different style of codebases needs to be handed completely differently.

Yep, the software development slows down to crawl. Yes, you can still code at the same speed as you were coding in a language like Java or C# but that is considerably slower then what's possible in languages like Ruby and Python.

To give you a roughly idea, you should always expect a 3x slow down when using static typing.

An recent example is Turborepo that went from basic types in Go to proper static typing in Rust. Just adding in the proper typing caused the codebase to grow from 20,000 lines to 80,000 lines and from 3 developer months to 14 developer months.

The stronger your typing system, the slower you will develop code. Whether you realise it or not.

"Wasteful unit tests that assert your types are right"

You don't test whether the types are right, you test if your code actually does the right thing. That's what's important to your customers.

The types getting tested is incidental.

Static typing doesn't have much value if there are proper unit tests. So it's fairly obvious that if people think there is value in static typing then they are shipping broken code to their customers.

It's called ratting yourself out.

And that's the problem, if you want your code to actually work you do need to write those unit tests. A program not crashing doesn't mean it does the right thing.

With experience you will learn to either write unit tests or spend the same amount of time doing manual testing.

Once you start doing that then the unit tests just replace the static typing and you start shipping better code to your customers.

Nah that's just a lack of understanding in the role of unit tests in dynamically typed languages.