But does this not make the assumption that the Identity being provisioned is exactly you and only you? I've always seen these identities as my pseudonym on some identity provider and use them in that manner.
I suppose I've used some identities in enough places that it would be hard to deny to certain entities that the identity was mine, but even in that case it's a small subset of entities which have seen the identity that could prove that it's me.
The founder of Leptos makes a pretty good argument [1] that the bottleneck for WASM isn't really the DOM and that they are already faster than some popular JS frameworks even with the current constraints.
Just tried the site, and already the first problem is isn't as interactive as the Websites for any JavaScript framework, because naturally there is a whole contraption to make the code run into the browser.
That's odd. I have been following along here [1] and it seems just as interactive as Svelte, Angular or any of the others I've tried. There might be a few more tools that have to be installed, but that's a one time step.
Where editing the code, immediately shows the GUI related changes on the neighbouring frame.
While what I see on https://leptos.dev/ is just screenshots, and there is nothing on that documentation you linked that provides the same interactive experience, one has to explicitly start a developer sandbox to host the whole machinery, and even requires a codebox account for editing.
That's what I was thinking. Or any application at all. If MS word started doing this, how long would it take to recognise? Especially if it's only periodic and only some small percentage of their install base.
I used to get a lot of tickets until I cruise control got reliable traffic detection. Now I have it on almost exclusively. The only places I get tickets now are usually places that the speed changes and I don't notice.
I would like to set my cruise control to just be "current speed limit". If these cars are going to start monitoring the speed limit to the degree of being able to tell if you're breaking the law, they better have such a setting. If they don't then it seems almost like some sort of entrapment.
blue cruise is amazing for that, though I'll note that there's a setting for how much above the speed limit you're comfortable with, so you could set it to 0, but you can also set it to 14 over limit and it'll cruise control quite well, turning and braking for you.
Might depend on where you live. Not all roads are created equal.
I'm thinking stuff like many posted speed limit changes within a short length, damaged or missing signs, non-obvious construction and school zones, road passes through varying types of neighborhood, speed limit unexpectedly low for the design, etc.
By far the most annoying to me are off ramp speed limits that are so unrealistically slow they'd probably cause rear-end collisions or pile ups if anyone actually tried to obey them.
Why are you presenting something that happened as entirely one sided? This move means the end of an enforced, curated walled garden for iOS. This will mean a race to the bottom for iPad apps. Which, of course, means even more ads (since everything must be paid for one way or another). It likely means iPad prices go up even more because now they're forced to support configurations they've never tested.
For me personally, all of the above is the cost and what I get is something I wasn't using and didn't miss (if I want to install things outside the walled garden, I use a my Mac not a mobile device).
> This move means the end of an enforced, curated walled garden for iOS.
Great! (Imagine having wallgardened Windows computer where you could not install whatever you want).
> This will mean a race to the bottom for iPad apps. Which, of course, means even more ads
iOS store is already at the bottom. Everything is with ads or subscription based. More ads won’t scare me because I won’t use app with any ads. If app offers one time purchase - I’ll buy it if I like it. Examples of apps I bought: Structured, Bobby, ArtStudio, MusicStudio.
> if I want to install things outside the walled garden, I use a my Mac not a mobile device
What if Apple decided you cannot install apps outdide off their App Store on a Mac neither? What would your “Apple-defending” argument be then? It’s NOT a far fetched idea. Microsoft tries it with Windows S Mode and they currently constantly threaten people when they download software from internet about how dangerous it may be, trying to scare people into using their store.
>Great! (Imagine having wallgardened Windows computer where you could not install whatever you want).
Again, you are presenting this as if it has only one side to it. I need a computer that has no walled garden for certain kinds of work. For other kinds of work I'm happy to know I can't break it. Even more important, I'm happy when my parents can't break the one I buy them.
>More ads won’t scare me because I won’t use app with any ads. If app offers one time purchase - I’ll buy it if I like it.
As long as such an option exists. But in a true race to the bottom situation, there may not be anyone willing to invest in developing an app and then selling for a one time purchase. One time purchase is a model that's nearly dead anyway.
>What if Apple decided you cannot install apps outdide off their App Store on a Mac neither?
This I wouldn't accept because I can't. It's a development machine for me. But an iPad is a consumption device, I need the thing to just always work.
Exception handling, for example, uses dynamic scoping since you don't know what will be handling your exception when you write code which throws it.
Another way of thinking about it is, with dynamic scoping the value of the dynamic variable must always be on the stack and the closest one is the value that will be used. This is a really good behaviour for global variables since a common source of bugs is some global variables (and I'm considering class members "global" for this) getting changed unexpectedly. If the variable is lexical then it can be very hard to figure out what changed the value (especially when threads are involved) but if the variable is dynamic it's easy: the culprit is in the stack trace.
Just noticed your comment now: Thanks so much for the explanation! However, my question was more about the blog post in particular, i.e. coroutines (async/await) vs. effect handlers: I still fail to see why coroutines are lexically scoped. async/await yield control back to the calling function which might or might not define an event loop or yield control to another function further up the stack. How is this different from handling effects or exceptions? Whose scope does "lexically scoped" refer to here?
EDIT: Ah, reading this comment[0],
> The more fundamental difference between effects and coroutines is that a `yield` in a coroutine always goes to the one unique resumer
maybe I thought too much of Python where async/await are implemented via generators and, unless I'm mistaken, there need not be a unique resumer/event loop.
> Leftpad is an entirely pure, non-diverging function. And I should be able to ask my language to enforce that, ideally with trivial code. Maybe even by default.
I think you can do this in Idris with "total" functions.
I think the GP meant polymorphism. Rust traits being static ad hoc polymorphism. I thought it was possible, though, to achieve the same thing with Functors. Just the standard library deliberately didn't and chose to have things like 'print_int', 'print_string' and so on instead of a Print Functor.
Yes functors would be the way in OCaml, but there's no implicit context resolution that implicitly resolves such symbols within a Functor the way you can in Rust or Haskell. This missing implicit context resolution makes for bad ergonomics, particularly for any kind of numerical code, which tend to be the very first kinds of things that new programmers try in a new language. "Hey, why do I need to use + in one case and +. in another? This is dumb, OCaml is not a serious language."
In OCaml the integer operations are implemented using LEA instructions, and the floats are boxed. The language is not really suitable for numerical code...
The only one who can have responsibility for anything is the one who has the authority. So long as developers are in a position of "just get it done or you're fired" as well as being outsourced to save costs, they have no authority in this and therefor zero responsibility. If management "doesn't know what we do" and doesn't want to have the responsibility then they have to give us the authority to say "no, this is not going to be done tomorrow and we're not cutting any corners".
> The only one who can have responsibility for anything is the one who has the authority
So if a cop gets an adresse wrong and is a bit too trigger happy and ends up killing innoscent people. Its their chief of police who should go to jail because they told them to go arrest a suspect? Unless we change the system to allow cops to just do whatever they want whenever with not leadership?
The idea that just because a programmer doesn’t have complete autonomy over their work that they suddenly become unaccountable for negligence and errors is ridicules.
Who actually works in a job like that? Do you seriously think you’re a slave to your boss, with no personal agency? Do you think your employer wants you to be feckless? Do you think that’s good for your career?
Your capacity to take responsibility is the differentiating factor between junior and senior engineers. Learn to step up. If nothing else, your pay check in 10 years time will thank you.
Incentives do matters. It should be pretty clear to anyone on this forum. The parent is absolutely right. Responsibilities do matter. In this case, there was clearly a systemic problem that was repeateadly ignored by mulitple levels of hierarchy.
You position is a position of principle. When peopke lives are at risk (boeing, fukushima and yes even the post-office) pragmatism must prevail. Those in charge must pay the price, otherwise you incentivise financial results over everything else. People die? Oh that's because Greg in engineering is an idiot, burn him!
The problem is with insufficient QA and processes in place. If a coder delivers code that is insufficiently tested before deployment, the onus is on the product owner. It's the reason "owner" is synonymous with "person who is responsible."
I don't know where you live, but in my (extensive, but rather local) job experience so far, it's possible to raise concerns and propose solutions, etc., but once the IT director or VP of whatever says "we're not going to do that", it's over. You have to work on something else. Or find whistleblower protection, and good luck with that. Otherwise it'll be "Can you step into my office for a minute? Close the door, please."
I suppose I've used some identities in enough places that it would be hard to deny to certain entities that the identity was mine, but even in that case it's a small subset of entities which have seen the identity that could prove that it's me.