petilon

What about rendering? That's the hard part.

The reports feature of Visual DB seems to have most of what you are looking for: https://visualdb.com/

It has sophisticated filters and you can share reports with your team (as opposed to exporting CSVs).

Time traveling humans is more likely for the following reason: It requires only one thing: worm hole or some other yet-to-be-invented mechanism for traveling to the past. For this to be alien intelligence, two things are required: First alien intelligence has to exist, and second, they too need a mechanism for speedy travel, to travel to another galaxy such that they can reach the destination within an individual alien's lifetime.

4. Time-traveling humans from the future. Don't discount that possibility!

Coinbase is the favorite tool of scammers, see for example https://archive.ph/PikUQ

...and Asus... and Dell.. among others

Weird... I have only ever seen this artifact on Windows machines, never on a Mac.

I have been to BestBuy and tried out laptops with non-integer scaling (150% or even 300%) and observed the display artifact I mentioned previously.

This 16 inch laptop has 2560x1600 resolution. If you set it to 200% then that's the equivalent of 800 pixels which is what you expect in a 13 inch laptop. For a 16 inch laptop there's not enough pixels.

Why set it to 200%? Because as Steve Jobs has explained, the only resolution that looks good after 100% is 200%. Then 400%. If you set it any in-between scale (such as 150% or 300%) then you will have display artifacts, such as horizontal lines appearing to have different widths when they are all in fact set to 1px.

200% means double the resolution of the "previous era" (1990s and 2000s), which was around 96 dpi. Modern applications will not see any scaling artifacts.

Applications from the "previous era" that are not HighDPI-aware will get scaling... each application pixel will occupy 4 physical pixels.

This Samsung [1] is only 14" and yet has 2880x1800 display. That's 200% resolution. Anything less than 200% is not interesting to me. iPhone with Retina display debuted in 2010. Isn't 13 years enough time for PC laptops to catch up?

[1] https://www.amazon.com/dp/B0BPJWYQSY/

Sorry your last attempt failed. If you have been following React discussions on HN you know there's massive criticism about hooks. MVC is still the predominant pattern and for very good reason. Backbone.js is not relevant for this discussion.

It is not sufficient if, in aggregate, self-driving cars have fewer accidents. If you lose a loved one in an accident where the accident could have been easily avoided if a human was driving, then you're not going to be mollified to hear that in aggregate, fewer people are being killed by self-driving cars! You'd be outraged to hear such a justification! The expectation therefore is that in each individual injury accident a human clearly could not have handled the situation any better. Self-driving cars have to be significantly better than humans to be accepted by society.

Sorry none of this makes any sense to me. You can't have cyclical data binding when you only have 1-way data binding. MVC is absolutely perfect for stateful use cases. In fact, it is React that suffers a total breakdown in stateful use cases. If your component is stateful and you need to update props then the recommendation is to set and change a key, which replaces the component with a new instance. This of course eliminates any benefit that React provides.

Famously, a Facebook engineer declare on stage that MVC doesn't scale. Later it turned out that she was talking about one specific implementation of MVC that used 2-way data binding. She assumed that 2-way data binding is part and parcel of MVC, because that's all she had seen.

See https://medium.com/@mckoder/why-react-is-not-functional-b1ed...

What about it is "functional-like"? Does functional simply mean not using classes?

Backbone.js used 2-way data binding. Some people mistakenly think MVC implies 2-way data binding. It does not.

The point here is that you can write maintainable, clean, efficient JavaScript web apps without the load of complexity added by React.

There is no two-way data binding in use here, so you're wrong.

The style used is MVC. Do you think MVC is not suitable for multi-person teams? If so how do you explain MVC in Cocoa, ASP.NET Core, JSP and JSF, Ruby on Rails, and Django (Python)? They are all based on MVC.

See the web app. It is a more productive style of coding. Simple, and no need to deal with hooks and useState and useContext and none of that nonsense.

> but the style of programming it introduced to many millions of web developers made a sizeable chunk of them interested in fp

Why would that be? React is not functional, and the style of programming has nothing to do with functional programming. It is fundamentally inconsistent with functional programming.

> a literal 5-20x productivity boost

Not really. See a better way here: https://github.com/wisercoder/eureka

Most US credit cards return 1%, some return 2%. Another advantage of credit cards is that the bank acts as a mediator in case of disputes regarding the charged amount. Also, rental cars and hotel rooms are only available if you charge them to a credit card.

When you pay cash you are paying for the credit card convenience (the fee that is built into nearly all price tags) without benefiting from it.

My bank returns 2% of the charged amount. If I paid cash I would forego this benefit.

What a terrible website. The components are not interactive. They have screenshots instead. And in the left panel when you click on an item you lose the scroll position, and you have to scroll down all over again. The controls and their design are boring as well.

What does this mean for Microsoft? Pretty much everything they do is a copy of some other successful product. Consider Microsoft Loop. Pretty good product. But it is a Warhol'd version of Notion. What is Micrsoft Teams, if not a Warhol'd version of Slack? What is C# if not a Warhol'd version of Java?

Very thin frameworks can avoid the complexities of React and hooks and useEffect and whatnot. Here's an app written with a 500-line "framework", notice how readable and maintainable it is: https://github.com/wisercoder/eureka

TypScript can't do that because TypeScript doesn't have any runtime. TypeScript is compile-time only.

That's like saying the following is incorrect

   let foo: number;

because at runtime you can assign a string to foo.

Typescript's type system is for compile-time checking, not runtime checking. The above definition is correct if at compile-time you want to check that all assignments to foo are of type number.

To be fair, around that time Musk had a high favorability rating within the whole industry. Musk seriously rotted afterwards. But prior to that time he was a different person, watch this video if you don't believe me [1].

[1] https://www.youtube.com/watch?v=TOMcCNNdSl0