Hipster languages/runtimes/frameworks

Go! Rust! (they are both comfy, but also reasonably hip so might be)... I hope PostgreSQL instead of mongodb

>>57808412
node aint no meme. My entire workload shifted over to node, management rammed it down our throats. Turns it it aint so bad.

>>57808412
lua

>>57808412

you mean node and js was the hipster language and now its go and rust?

>>57808412
>>57809670
>>57809969

I thought it was already Go and Elixir/Phoenix where webhipsters are at now.

Whats next?

>>57808412
But node is a good thing

>>57810000
If you like languages that actually run on a single thread internally.

>>57810000
waste of quads

>>57809932

this

>>57810133
>>57809932

They already tried and it didn't work. And boy, it's not like they didn't try, but all the frameworks so far failed in one or another way:
http://lua.space/webdev/the-best-lua-web-frameworks

>>57809998
Assembly web development

>>57809901
Just because hipsters like it doesn't mean it's bad. It just means that it is uncool for people who think of themselves as "real serious programmers" the hipster language might be great

>>57809932
Lua's library/module/whateverthefucktheycallit is pretty weak, so it will never take off for this sort of thing. It will always be an embedded language (thank God. It will keep the cute language safe from shitheads).

hipster shit is go and .net core/asp.net right now.

webframeworks build on both solve a job that php/ruby/js/python solved for decades.
on the rest service side they are coming up against node and boy finding maintained packages for this shit is stupid.

personally i use non of this shit, thats what my hispter web colleagues tell me.

up to last month i was am stuck on porting a giant shitty engine to open gl because muh mobile.
its now become simulatniusly porting it to vulkan because management is not ready to abondon two years of work

right now iam looking into rust because i haven't its package manager cargo has some good shit,
but i feel like a webdev hunting packages instead of writing it myself sometimes

worst part is i wanted to start using it because of mobile and the toolchain is terrible to get it on there.

software is terrible

>>57810426
Standard library you mean?

Well yeah, there's a reason it's just 1MB or something at the basic implementation (LuaJIT)

>>57808412
It will always be JS as long as JS is the language of webdev. Hipsters love webdev because it's not really dev at all, it's just plugging values into templates. Reminds them of their childhood toys.

>>57810585
No, not the std lib (which is mostly a la carte from C anyway.)

I mean there's not a good package manager, and the system for "importing" other lua code is pretty poorly defined. So you wind up just doing it all yourself, or leaning on the host language (as intended, ofc).

Also
>LuaJIT
>in anyway basic

No, Mike Pall is a wizard who wrote the interpreter in x86 ASM. In no way is it "basic".

>>57810649

Well, the 'barebones' implementation is what I meant.

Sorry, it's 2am, I'm drunk and half messing around with torch in background.

>>57810723
I still don't see what you mean. LuaJIT has more features as well.

The official libraries take up less space, but run slower. I would call them the "barebones".

>>57810000
the core is good but npm and package usage in general for nodejs projects is cancer

>>57810649
>not a good package manager
fuck that shit
why does every language have to have their own package manager just for that single language now?

now all projects depend on dozens of small buggy third-party libraries

>>57810856
I'm not saying it's a BAD thing, you mong. I'm saying that's why it won't be adopted by hipster web developers.

>>57810881
I haven't even followed your discussion.
That shit just triggers me.

>>57810856
>why does every language have to have their own package manager just for that single language now?

If you have to ask that question, no explanation will convince you otherwise.

>>57810835
it's only retarded because it's not completely unified.

>>57808412
I would say it's good for prototyping, but not dependable enough for real use cases.