Jouke

[Jouke @MisterAwesan]

@justinfagnani It still makes sense to then define both of those and to explicitly force the standards committee to consider how high-level feature can be implemented in terms of low-level instructions.

[Jouke @MisterAwesan]

@ashtom I'm sorry but when you're at the point that you know a particular function has a performance problem, surely you don't need a computer to tell you how to fix that? All the hard work happened before clicking the button?

[Jouke @MisterAwesan]

@the_dijkstra A "singleton" is a class of which there is only ever one instance. I think in this case the term is used to mean something completely different? (the passed func is called once per component lifecycle). Very confusing IMO and dangerous.

[Jouke @MisterAwesan]

@YvanBrunel @JenMsft @salsawithcheese control clicking also works in the sidebar but not in the main window. indeed scroll clicking does work.

[Jouke @MisterAwesan]

@JenMsft @salsawithcheese They don't seem to have much of the behavior you'd expect of tabs tho; for example Ctrl+DblClick does not open a folder in a new tab (new window instead) and when some process opens a folder, it defaults to a new window as well. In practice I never use them for this reason.

[Jouke @MisterAwesan]

@maxlynch I guess it's a matter of emphasis but how can you do one without the other? Code quality is relative to the needs of the user. And trade-offs involve code quality and technical understanding.

[Jouke @MisterAwesan]

@nullvoxpopuli Why not, those warnings have basically never predicted any true problems for me. Even if you install a new ember project on the latest ember-cli with all default values you get some of them.

[Jouke @MisterAwesan]

@nullvoxpopuli VSCode has it in the bottom right, similar to how nr1 works. I can't really tell but IMO changing the file type is not something you do a lot and it should not be anywhere near (1) actions you use a lot (2) places you look for frequent actions.

[Jouke @MisterAwesan]

@nullvoxpopuli I always have BS issues like this with linux across many distros over the years, and I see it also with people around me who use it. At some point you just learn how to deal with it and barely notice anymore but things still constantly just break for no reason.

[Jouke @MisterAwesan]

@nullvoxpopuli @frederic_ooo @signal why not just the decorator without the "accessor"? is the reasoning written anywhere?

[Jouke @MisterAwesan]

@Andrei_Calazans this is the same in any other language no? it's the only sensible behavior on empty arrays.

[Jouke @MisterAwesan]

@JenMsft @sahilmalik Is this new? I've wanted to disable the news since the widgets exist and I was never able to find an option for it.

[Jouke @MisterAwesan]

@nullvoxpopuli There's not enough room in a tweet for me to explain but essentially it depends on the value what should happen on reads/writes to the signal and that is domain specific. You very quickly hit that as you implement. There's no generic solution for this so the complexity explodes.

[Jouke @MisterAwesan]

@the_yamiteru @still_runspired It happens all the time if you're testing something and want to comment out a line... It's extremely annoying if you can't do that and need to delete it instead.

[Jouke @MisterAwesan]

@rikarends It makes sense to plan for multiple possible outcomes. For all we know AGI takes another 20 years or never happens. There's little to lose by thinking 10yrs ahead regardless. Also.. IMO society is not likely to end quickly. Much more likely to be a slow decline over many years.

[Jouke @MisterAwesan]

@y_molodtsov @nbaschez This is total BS, people at the time were pretty loud in complaining that the iphone missed very basic features (despite it being somewhat useful). This only got resolved when they released the app store, *years* later. Mass adoption also only happened after the app store release

[Jouke @MisterAwesan]

@nullvoxpopuli Learning what's important vs what's just boilerplate also puts strain on new learners so in the end it's just a trade-off IMO with no clear answer. Ultimately will be a matter of preference.

[Jouke @MisterAwesan]

@nullvoxpopuli A bit of convention is necessary to learn anyway and doesn't hurt.. for example component names mapping directly to file names is not a big deal because you need to learn it instantly and it makes sense. That would cut over 60% of this list.

[Jouke @MisterAwesan]

@nullvoxpopuli I'd love a tracked query param primitive (usable from anywhere) and a tracked local/session storage primitive. For persistence these things would be major productivity boosts in a lot of cases because you probably start out with just @.tracked when building the feature at first.