fultonfaknem42

Confusion. You're experiencing confusion.

I get the exact same thing.

They're totally worth it.

I can't help but thinking about the 5 monkeys and a ladder.

https://www.wisdompills.com/the-famous-social-experiment-5-m...

(Even if it is bullshit)

You could do the math if you look up the half-life of caffeine. Via a quick Google search it looks like it is 4-6 hours. So if I understand it correctly, it's 4-6 hours for 100mg to become 50mg, then another 4-6 for 50mg to become 25mg, etc. So like if all you did was have a single cup of 100mg coffee, then its like 12-18 hours for it to go away. If you're me though, you drink like 3-4 a day. This seems to be about 28 to 42 hours. Withdrawals could take up to 2 weeks in my experience, and are proportional to how heavy my intake was.

I would love to produce my own ClearView.

I can't answer your question exactly. I came around only after Cocoa was established.

This does make me wonder if the transition from Carbon to Cocoa is analogous though. Win32 comes off as more of a "functional" approach to programming (C) and UWP is looking more object oriented (as to C++). It makes me wonder what kinds of conceptual advantages are being brought on board by moving from win32 to UWP. I think that conceptually I am in favor of the transition, and I'd wager that all the issues that arise are common to a functional to object-oriented transition.

But that real questions: What are the benefits? Is it conceptually easier to grasp thus promoting more developer interaction? Are we expecting speed benefits (are the performance losses expected and in range?) Is it a false dichotomy to only look at Functional vs OO? Maybe a context-oriented data approach is more appropriate?

Dunno.

They have obstacles to overcome, and then there is just the glaring fact that they had so much momentum with Win32.

My biggest gripe is that startup times are just too long. So many times I've gone to launch something like calculator only to have a beefy machine hang for almost a second, if not a full second. It's likely an engineering obstacle that can be overcome but it just makes UWP look like a bad move perf wise.

It looks like no one even cares about the drama of this.

I'll second the API being very well designed. It is incredibly legible from a technical perspective and it has actually been generally a joy to figure it out, as opposed to just being told how it works. That being said: I need some bathroom friendly reading material every now and again.

That is interesting and counter to my experience. Consider looking in to alternative causes (uninstalling plugins that may not be playing nicely with your particular version, background updates, etc.)

Given the new mission statement of Microsoft, I think if the community is more vocal about the things they want to accomplish it will become imperative that people at the company will be assigned to making those desiderata a reality. So if you want more visual tooling, find a way to become more vocal about it. If you want more support for this or that tech fad, make it known.

This looks like a pretty cool demonstration of what we're talking about: https://www.strathweb.com/2019/01/collectible-assemblies-in-...

See the section titled: Collecting a dynamically emitted assembly

I think ignorance is a pretty powerful argument to be made by any developer wanting to use Roslyn. The last few times I messed with it there was literally no documentation and everything I knew/know comes from reading headers, trial and error, and experimentation.

I feel defensive about calling it cumbersome though, and I can't imagine why something like your LUA vision isn't possible (though, I've never tried I just assumed someone would inevitably do this). For example, if World of Warcraft were to switch out their UI LUA extension system with C# I could totally imagine this being possible (though it'd be suicidal for their mod community). Likewise, if Unity were to begin using it for this kind of thing (if they don't already) I'd imagine it is possible.

Maybe Assembly unloading, in which case if you wanted to swap out new dlls in memory you'd have to tear down the process and restart it. Definitely not sexy. That being said: I think Assembly Unloading is a thing now (and AppDomains don't exist in .NET Core last I heard).

I still can't believe more people aren't leveraging the Roslyn APIs to write compiler extensions or additional tools around C#. It's conceptually powerful.