https://news.ycombinator.com/item?id=33140210
The “startups” in the US are even bimodal. You have the ones that set up shop outside of the west coast in big cities that hire “enterprise devs” and you have the well funded ones that try to compete with big tech salary compensation.
As I said, very few new companies that aren’t “legacy” shops are choosing .Net.
In my current job in cloud consulting at $BigTech, almost all of the .Net projects that come through are older companies compared to newer companies that are using non compiled languages.
These days I write in almost any language they prefer among the popular languages.
“My field” is a 20+ year MS ecosystem developer from
C++/MFC, VB6, .Net Compact framework, .Net Framework,
.Net Core, etc.
Right, and in that field you might be correct (I don't know but I'll take your word for it). It is however not the entire software industry. As I said, very few new companies that aren’t “legacy” shops are
choosing .Net.
I'm a game developer and the most popular game engine (Unity) uses c#. The newest up and comer (Godot) uses their own scripting language or c# as the most popular options. I've also worked in Enterprise before and c# and java were the popular choices there and as far as I know from friends still are (especially when servicing the government)In the US, the companies that pay top dollar - the large tech companies and well funded VC back companies are not adopting tech companies.
That unfortunately hasn’t helped C# become more popular outside of
Microsoft legacy shops even when it did go cross platform and open source.
Where I work is very much not a microsoft legacy shop (a game dev startup) & we use c#. This is hardly unusual.https://news.ycombinator.com/item?id=33140210
When talking about compensation, it might as well be an “enterprise shop”
Just in case you don’t read the link above, that’s not meant to be derisive. It’s just a pure statement of fact.
There are plenty of “startups” that locate in major cities in the US outside of tech hubs, find a bunch of MS developers to write the next CRUD SaaS app and pay enterprise dev wages. I should know, I spent over two decades working for them
I think you would get a lot less pushback by simply using more precise terminology- even though for you it may all be the same, for people working outside of FAANG-esque companies it isn't.
In the US though, compensation for software developers is very bi-modal. You have the “enterprise shops” that start off around $80K and max out in the mid $100s and the “tech companies” that start out in the mid $100s and end up in the $350K+ range.
Most of the 2.7 million developers in the US are on the “enterprise dev” side. If you have a choice, you want to be on the “tech company” side if you care about your compensation.
For context: because of path dependencies and bad career choices, I spent most of my career from 1996 - 2020 on the “enterprise dev” side and only got into $BigTech by pivoting to cloud consulting (enterprise dev + cloud + a shit ton of yaml/HCL PowerPoint slides and diagrams)
Before anyone “well actually”’s me with numbers they are directionally correct on the enterprise dev side in most major cities.
Actually I thought of using C# a few months ago, and I was like "Oh wait, does it even work on other platforms than Windows now?". Sure I'm not a C# developer, so I'm not up to date on C# news, but that's an issue if your goal is to drive adoption. Everyone that has heard of C# should know that it's now cross-platform.
Other than that, and other than the obviously Windows-specific GUI and system management libraries, the rest of C#/.NET is pretty much fully multi-platform, maybe except a few obscure things.
I think Godot also supports it
i.e. "it stays out of your way if you don't actually try to use it"
"go to definition" -> goes to type definition
Microsoft makes it intentionally impossible to get anything done in their ecosystem without having "great tooling".
Java does it too?
It is so liberating to type a variable as `any` when sketching new code, figuring things out, that I would venture to say that any language not having the `any` type actually actively hates the developer.
[1] https://www.typescriptlang.org/docs/handbook/2/everyday-type...
Same. Like normal people do when they use Visual Studio/IntelliJ/QTCreator
aint fitting ten megs in a peek view... :(
>You can import JS directly into TS
Using FFI, you can also import all compiled languages into each other, provided you provide the type annotations on the importing side. Does that make them supersets of each other?
>use ts-ignore annotations
Which do not get propagated into the compiled .d.ts. So if you're trying to publish a library with TypeScript, you know, like this thing called "open source", and naively expect it to work like a normal NPM package does, you're in for a bad time. You'll probably end up using a frontend bundler to smash the whole thing into a CJS monolith like an absolute genius, in the process preventing "muh tree shaking" downstream.
I hope not.
>Using TS, you can import any valid JS module without any special preparation
Why does the DTS ecosystem exist then (https://www.npmjs.com/package/@types/node etc)
$ echo "export class Foo { a = 1 }" > test.mjs
$ npx ts-node
> import('./test.mjs').then(console.log)
error TS7016: Could not find a declaration file for module './test.mjs'. '/home/user/Lab/test.mjs' implicitly has an 'any' type.
$ npx ts-node -O '{"allowJs":true}'
> import('./test.mjs').then(console.log)
Promise { <pending > }
Error [ERR_REQUIRE_ESM]: require() of ES Module /home/user/Lab/test.mjs not supported.
$ echo "module.exports.Foo = class Foo { a = 1 }" > test.cjs
$ npx ts-node -O '{"allowJs":true}'
> const { Foo } = require('./test.cjs')
> Foo
[class Foo]
> new Foo
Foo { a = 1 }
> function bar (foo: Foo) {}
TS2749: 'Foo' refers to a value, but is being used as a type here. Did you mean 'typeof Foo'?
No I did not, TypeScript, and that's about as much as it seems to interoperate. I guess in some cases practical migration might be viable - but as for the general case, the out-of-the-box experience seems to speak otherwise.It's not even viable to write in JS and manually write a DTS - no way to check em against each other. Except idk library in JS, test suite in TS anyway. So not a lot of lateral movement possible in practice.
Try this:
// tsconfig.json
{
"compilerOptions": {
"outDir": "dist",
"module": "es2020",
"allowJs": true
},
"files": ["index.ts"]
}
// index.ts
import('./test.mjs').then(console.log)
> npx tsc && node ./dist/index.js
[Module: null prototype] { Foo: [Function: Foo] }Yes, it imports the module. No, it doesn't do even basic type inference (knowing that Foo is a class and consequently allowing it to be used as a type name) - which it would, if it was a superset of JS. Instead it seems to import everything as "any", which is... a start, I guess?