Hacker Newsnew | past | comments | ask | show | jobs | submit | seabrookmx's commentslogin

I know devs are a different market, but how many folks do we know daily drive Mac/Linux and use MS dev tools? VS Code, Typescript, .NET?

I think they'll do just fine if Windows dies on the vine. They'll keep selling all the same software; even for PC gaming they already have their titles on Steam.


GTK apps can be written in pure C. GTK itself is.

Citation needed. For both the existence of said people (how do you develop said design sense without a ton of coding experience?) and that they are 100x more productive.

If you produced 1 line of code per hour before "AI" because you suck, and now produce 100 lines of code per hour with AI, you are now a 100x programmer.

I'm joking of course, but that's probably how some people see it.


No I think you're 100% correct. But these people also miss out on the irony that using "lines of code" as a metric is a literal meme amongst software developers.

Depends on your definition of "use." They use an internal async fork, and don't use the ORM: https://djangochat.com/episodes/django-instagram-carl-meyer

In Instagram's case, they do not use the ORM or Admin, and have an internal fork of the request handling/middleware stack that is 100% async (before the recent async bits were added to Django)[1].

It's great that Django's API design allowed them to move this way easily, but they aren't actually using Django in the traditional sense because it can't handle their scale.

I've found that with the Django ORM and DRF especially, it's very easy to create a poorly performing app by following the established patterns (N+1 queries being a huge problem created by DRF serializers). You need to be extremely diligent to create something performant in this ecosystem. Not every dev team has Armin Ronacher :P

Where I work we found this exhausting, and moved on to FastAPI and ASP.NET. We make our queries much more explicit using tools like Dapper, and now a senior engineer can have a much better idea how a particular route will perform just by reading the code (obviously, we still do some profiling).

[1]: https://djangochat.com/episodes/django-instagram-carl-meyer


It looks like the next release of Django will take seriious strides to solve a lot of the n+1 headaches, https://docs.djangoproject.com/en/dev/releases/6.1/#model-fi....

Also, I doubt solving Instagram-level scale issues is on the top ten list of concerns for this project. Just getting something out there and gaining users is way more important than solving far future scaling issues.


Oh I agree 100%. Use the right tool for the job. I'm just saying, the "<hyperscaler> uses <framework>" logic is rarely useful to justify anything.

Valve has a containerized Linux runtime (ala flatpak) to solve this issue for native Linux titles: https://gitlab.steamos.cloud/steamrt/steamrt/-/blob/steamrt/...


Valve is working on this problem for native Linux games: https://gitlab.steamos.cloud/steamrt/steamrt/-/blob/steamrt/...

This is a similar idea to flatpak/snap etc.


You're assuming no game studio would test their windows executable on proton, just because they develop on Windows. If there's non-trivial market share to capture by being "Deck verified" I don't see why that would be the case. Game devs develop on Windows for PlayStation, Switch, mobile etc. At least with proton they don't even need to cross compile.


I am willing to bet that most don't give a damm about Proton.


Microsoft test on and make considerations for Proton for a bunch of their releases. Sony do too. Cyberpunk has specific graphics presets, Baldurs Gate 3 has a native executable, indie games often do too.

There's outliers, it'd be fair to say EA don't give a damn. But a lot do and you can't handwave away Microsoft and Sony as small fish either.


Is that a fair comparison? It seems like people have a compelling reason to use Linux (hardware compatibility, avoiding MS spyware, price, etc). I admit it was before my time, but what was the draw for OS/2? Even it's technical superiority to Windows was gone as soon as NT dropped right?


I've been really enjoying ruff/ty on my non-Django projects. Was there anything special you had to do to make ty play nice with Django? I kind of assumed with how dynamic a lot of its functionality is ty would just throw a type error for every Model.objects.whatever call.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: