Besides,Isn't typescript developed by the same people who made C# and also takes quite few inspirations from it?
870 karma · joined July 14, 2022
Besides,Isn't typescript developed by the same people who made C# and also takes quite few inspirations from it?
Arguably one of the biggest downsides of c++ is that it has tons of features without there being a syntactic sugar for using them, which in turn makes them less attractive
Why? If all Your work and knowledge is confined in one repo, there still is a way to work only on that part. Or at least there should be.
But if You want/need to have access to other parts, it's much easier to use monorepo then to search trough 100 of github repos that are somehow dependent but it's not obvious in what way.
But yeah, point still stands
You can reboot into uefi directly using console command. Don't remember exactly syntax from the top of my head, but it's trivial to find it online
Doing it as a 'post-process' will most likely result in just another layer of semi-grifting "specialists" that will come up with over complicated "solutions" that focus on masking symptoms rather then actually tackling underlying reasons.
Now, ofcourse, there are still 'good' abstractions and bad ones. But even the best one, by definition, hides some details away.
As for the article itself - I do agree that it is mostly a fluff, and not something revolutionary. But also nothing to criticize it for, either
The main difference is that with cpu, the translation unit is hidden inside the cpu itself. With gpus, the translation is moved from the device to the driver.
Old openGL code also will run in card that is newer then code itself.
The only difference is that with the cpus, it's open standard what is the instruction set, while on gpus, instruction sets are defined by third parties (DX12,Vulkan,OpenGL) while it falls to nvidia to implement them.
Altough ofcourse CPU's instruction are also just a frontend api that behind the scenes is implemented using microcode, which probably is much less stable.
But the point is, if we could move one level 'closer' on gpus, just like we have it on cpus, it would stop the big buisness gate-keeping that exsists when it comes to current day GPU apis/libraries
I don't really know how this should be dealt with.
...or maybe it shouldn't. And we should just accept that random minority will have their livelihoods destroyed. After all, it wouldn't be the first time when society disregarded injustice of few for the convenience of the many
Yes, people don't care nearly as much as we like to pretend in online debates
My point is that I just feel like "but someone please think of the ̶ ̶c̶h̶i̶l̶d̶r̶e̶n̶ memory safety" argument is over blown. There are ways to eliminate majority of those issues in cpp as well, but people simply don't care.
If You want to use Rust because it's just better language - go for it, I do it as well. But let's actually use that as an argument, instead of hiding behind superficial ones
Compared to what? Itself from 20 years ago? That's great, but not nearly enough. Cpp just has SO MUCH FRICTION that it's simply not worth it to deal with it. Maybe if you have 20yrs of cpp experience and carved out a specific way for yourself to avoid all of it while still being productive... But that's not really an argument.
And sure, there are still some cases when the alternatives aren't ideal either (ie. Rust also having friction, especially in domain like games, or higher level languages being too slow). But cpp has so much downsides I don't see why should one ever default into choosing cpp, unless you REALLY care about the benefits it brings. But those upsides are usually external (ie. ecosystem), rather then features of the language itself
The 'we analyzed the issue and decided it won't be fix' Is NOT the same as 'we don't cate about this, go talk to some other team and maybe they'll fix it'.
Deciding something is not a bug is not the same as just ignoring the bug and not fixing it
I think we shouldn't assume that there is no place for generalists 'low on the ladder', because with such bellieve we will implicitly ignore the proposals advocated by the 'low level' workers, who are actually the one who have to deal with the workflow obstacles every single day.
Thank You for the article!
I feel the same can be said about accessibility service: Once you get the accessibility permission, you have FULL control over the user's device. They could just split those permissions and expose a more fine-grained control api, but they (I suspect) have some one, verry extreme use case in mind and design the service around it (like ie. phone user being completly blind and requiring the accessiblity app to be an interface for literally all interactions with the device).
Which means that whenever you want to use some feature of that api, you have to trust an app completely and give it a carte-blanche to do whatever it wants on your device.
Which ultimately leads to gigantic whole in platforms security, for no other reason then 'this is the way and scenarios we intend people to be using it, and we give no compromises for anyone who has any other usege in mind'
In situations where it bypasses things like parental control its fair to bring it up as an issue, but it's not exactly a 'vulnerability' in the way a vulnerability is commonly understood