That's fair, but just take a look at how complex latest biggest hacks are like
https://googleprojectzero.blogspot.com/2021/12/a-deep-dive-i...
1,007 karma · joined May 15, 2020
That's fair, but just take a look at how complex latest biggest hacks are like
https://googleprojectzero.blogspot.com/2021/12/a-deep-dive-i...
kernel's code is terrible mess by java/c# web app standards (dependency injection, interfaces, mockability, testability, etc)
Even C#'s compiler code written in C# is below architect's dream web app code base full of DDD, various patterns, CQRS, Event Sourcing yada yada
then probably yea, but when it comes to skills?
I'd say that they're not really that unknown - https://ctftime.org/
Lua, JS and LLV IRM?
but the only things that make me really, really strongly consider getting smartphone is some form of Maps - let it be Google or something
and ability to send&receive pictures (MMS suck)
It's definitely possible to live with dumb phone, but stuff like maps, sending pictures and maybe access to email are sometimes incredibly handy
What makes you think that Slack's loading times is due to Electron, not shitty backend?
This is genuine question
Hmm, I don't think this is true.
Also this is kind of different beast - WASM has some limitations that need to be overcome
Google Maps performance seems to be way worse
I do wonder how's the WASM performance
as trying to write it yourself
and then reading about how other people do it e.g VS Code blog
https://code.visualstudio.com/blogs/2018/03/23/text-buffer-r...
Meanwhile writing your own libraries, parsers, compilers, oh boi.
Additionally it gave me waaay more than LC stuff, especially when it comes to learning system modeling / proper OOP
I worked in system like this and I actually loved that, especially that those were night shifts
I'd really take 3(+1)x 12h nights over 5x 8h
What if we allowed HTTP GET Body?
So what actually?
apps that didnt use GET Body, will not care anyway
apps that will use HTTP GET Body will be checked anyway
So, unless somebody downgrades HTTP Server then what could be the problem?
>^We're going to assume normalized words, which are all lower case and no punctuation, comprised of English letters from the 26 character alphabet. Getting the set of all of the possible words of any given length, is also quite an exercise.
I hate solutions like this because they'd never be even close to being viable in real world
Haha.
Actually HN seems to be least technical community (when it comes to arguing) out of all those I know (reddit, forums)
Discussions raaarelly *try* to go into the technical details, let alone deeply. I don't think I've seen more than 5 code snippets over year on HN
Not only HN's format doesn't favor this kind of discussions, but also it seems that people prefer more "abstract" more "fancy" topics
Damn, I hate this too
What would replace those?
Abusive/Maniac users are the problem too
iirc there were some changes around .NET Framework -> .NET Core to how does it work (where packages are stored) and that's why I said that since .NET Core I didn't have problems with it
and it really feels as if that was written with tooling in mind, really impressive.
Just because JVM or CLR are complex, then it *doesn't* mean that writting good C# / Java requires you to be proficient at CLR/JVM lvl and because of that it is hard.
>meaning a newbie devlopper can produce something halfway baked in these languages relatively quickly.
Newbie developer can produce mediocre solutions in all of those - C#, Java, C++.
The difference is that in C#/Java world it may be slow and in C++/C world it may be exploitable (more likely) <snark>.
Anyway, in my world very often it's not about internals, but about modeling skills, about OOP, testability. Those are some of the ways of measuring how good the code is.
Good system modeling skills are way above technology
What do you mean? since .NET Core it always worked flawlessly for me
>unacceptable code formatter
hmm? that's preference not an argument.
I didn't spent a lot of hours in C++ world, but it never felt simple
- N compilers, N package managers, N ways to do everything
I've spend probably 20-40 hours with those and I must say that I like "normal" programming more
By "normal" here I meant that you don't have to be some kind of genius in order to model real world using OOP.
And we have shitton of programmers that everyday model real world complexities using OOP
>Wasn't that whole concept just marketing by Sun to sell Java and OOP to the world? These days everyone using Java uses so much spring and xml I'm not sure it even makes sense to call it OOP anymore. It's more like AOP+DI with a little OOP thrown in.
Well, on the other hand C# doesn't have all of that XML fetish/Annotation Oriented Programming (@Transactional :P)/Aspect Oriented Programming magic, so it's not like there's only one interpretation and implementation of OOP and it must be Java's