Readit NewsI think folks who write languages should have a typographer on their team because something like this:
use std::collections::HashMap
Is a typographic nightmare. While I understand “form follows function”, it’s tough to be excited to program in something like this.
If I understand correctly, GATs are about being able to change compiler assumptions about data types in user code? Generics acting on the compiler?
How is that helpful? Is it that you're trying to skip all the language boilerplate around creating objects? Are there any risks/footguns to that approach?
Generic type-driven code makes my head hurt, let me know if I'm somewhat close
GATs allow traits to abstract over associated types that are themselves to some degree abstract. In this case, it's necessary to do the relevant trait machinery around lifetime transformation since we need to be able to talk about "a replaceable lifetime of a type" in a generic way.
What are the compiler bugs you ran into? I'm no compiler expert, but my suspicion is that they were more feature requests than anything else, considering you're working in a "here be dragons" area of the map.
The bugs in part 1 all around using higher ranked trait bounds. I'd disagree with the characterization that they're "feature requests": five years ago, yes, I would agree, but this entire area of the compiler needs to be bug-free for an upcoming feature (GATs) anyway, and indeed, the issues I found were often fixed by people working on fixing related GAT bugs. Ultimately, my use of higher ranked trait bounds is an attempt to emulate some of what GATs get you in stable Rust, so it's not surprising that the bugs are in the same area of the code.
That is total BS. I had promotion multiple times just because business owner liked me and valued my work.
>You have to be performing at the next level for several months
Total BS too. Maybe in India.
> VISIBILITY
This one is not BS! I have seen many many developers without any rise - just because they do not attend any meetings, they look like bumps(no suits!), and those who do not talk much with their own boss or boss above...
When I manage to do something BIG - i make sure that my boss, his boss, and boss above KNOWS that we tried hard and delivered. It's not a shame to brag about real accomplishments :)
In that way I received 32% pay-rise in past 2 years.
This has been the case at both my current and previous (American tech) jobs.
And it's pretty racist to assume that a person is working or has worked in India just because they have an Indian name.
Deleted Comment
Any idea?
It also produces an interesting coherence:
Google + MS -> Blink
Apple -> Webkit
Linux -> Servo
All the main OSs now have their own web rendering engine.
The 00s saw anti-trust against MS for this practice (ok, for the rigid way MS forced their engine onto their users)... but today the market has coalesced around the same core idea, cementing the notion that general purpose OSs need a web rendering engine.
Might this pave the way for a better cross-platform UI development? Rather than shipping Electron to every device for every app, apps might leverage the web renderer tied to the OS?
I'm just wondering out loud. I was actually hoping we'd collectively move back towards native apps with better cross-platform tools, rather than integrating web apps deeper into OSs (even tho' I'm a web developer by trade and stand to gain from this).
The "Linux" there is more of an indicator of its origins than its purpose.
Most of the graphs here are about new code.
[1]: https://security.googleblog.com/2021/04/rust-in-android-plat...