highwind

You can't beat serving useful data to the user on the first payload (base HTML), no matter how fast or clever client-side rendering gets.

Business days/hours are currently labeled using the time system based on solar time: We are open Monday~Friday 9AM~5PM Saturday 11AM~2PM etc.

Without timezones, this would be really confusing. You'd have to say something like "We are open from Day1 9PM until Day2 5AM, etc." which can be annoying.

Maybe this? https://www.washingtonpost.com/business/2018/07/16/amazon-pr...

You could ask people to flag the ones that are not humming and if a user is flagged multiple times you ban that user.

Being a consumer product and a museum (art) piece is not mutually exclusive. Lot of classical music and classical paintings were commissioned with a price to be "consumed".

> But archeologists aren't going to use it in 5000 years to understand contemporary (to now) culture.

Why not? While that particular hardware on its own might not explain the culture but knowing what people consumed as an entertainment and what people tried to invent for entertainment seems like a important thing to know to understand a culture. (This logic can be applied to classical music/painting)

I'm confused. Can you tell me how your comment relates to the article?

The author of the article is sharing his experience with Haskell, explaining ups and downs. He concludes by

> Haskell is a great programming language. It requires some effort at the beginning, but you get to learn a very different way of thinking about your problems.

Are you interpreting the word "different" as "better"?

I personally find using two hands for pressing key combinations more comfortable than holding a modifier key with a pinky and reaching for the other key.

Maybe he means in browser Java Applets. But they are pretty much dead anyways.

It could be a style choice. Being more specific makes it feel more real, at least for me. Making it general sounds detached.

It's definitely not a proof of concept.

> Our long-term plan is to:

> - Incrementally replace components in Gecko with ones written in Rust and shared with Servo.

> - Determine product opportunities for a standalone Servo browser or embeddable library (e.g., for Android).

https://github.com/servo/servo/wiki/Roadmap

I guess the changes happen too slow for a single person to notice within a span of single generation. So I guess I'll have to die in hopes that I have done my duty to change the world for the better and the next generation will carry the torch for me.

As far as I know, all CoffeeScript did was add bunch of syntactic sugar on top of JavaScript.

I believe Kotlin actually adds programming paradigm that's not in Java on top of terse syntax, i.e. real closure, operator overloading, pure object orientation, and more.

> I'm not buying you couldn't make a decent, self-contained, off-line speech recognition system.

I agree. It's not a problem of technology, it's a problem of incentive. There's no money in developing self-contained, off-line speech recognition system, unfortunately.

All x should be y is a bad statement to make, especially if you are an engineering. Every problem domain is different. And every choice has pros and cons.

Doesn't principle of optimality state that if a solution is optimal than any of its sub problem must be optimal as well?

Why not both? Learn from highly specialized experts. But since even the experts are not free from their personal biases, supplement the knowledge with 'wisdom' of the crowd.

Could you provide some examples of other choices that you speak of? Thank you.

Tell that to Oracle. https://i.imgur.com/fQ6pQLn.png

Irrelevant might be too strong of a word. Yes, it might not be as significant as your own problem solving skills but they are still important. You have to remember that tools chosen by you to solve problems.

You wouldn't say what tools you use to build a house is irrelevant only carpenter's skills.

Picking the right tool for the right problem is part of problem solving. Sometimes picking the right tool might boil down to what you are most comfortable with, or sometimes it might be learning a tool that you are not familiar with.

(Of course, you shouldn't flock to a particular tool just because someone else said so.)

Anyways, picking the right tools are important part of your problem solving skills.

Graham and his buddy were good problem solvers who picked the right tool for the problem that they were solving.

It's OK to have similar/duplicate things on the Internet. (It often is the case.)

I think they just inject iframe into the actual DOM. It's not an UI element that's part of the browser.

Actually they link to the Diagnostic page for the malicious site.

Then again, one cannot expect all of any website's client devices to have a correctly calibrated displays. Unless you have control over entire stack (from your service hardware all the way to client displays), you have to start your design (graphical or otherwise) with the assumption that there will be differences in how your product is perceived by your clients.

Ugh... just scrolling through that page adds TON of baggage in the browser history. So much for the back button.

If I didn't click a link or a button, don't add things to history. Please.

The part where Cosmos, the player, manipulates the memory to execute arbitrary code starts around 8:06 mark.

Know More is a pre-Bezos product. Bezos took over on 10/1 and know more was launched on 10/7. Meaning planning and development on Know More must've started before Bezos' control.

I'm not sure if I like introducing computer science with a physical "computer". A physical "computer" is an application of computer science. I rather start with an abstract idea of computation, but my view point is very skewed towards academia. I'd love to hear what others have to say about this approach.

Why is the password limited to 16 characters long? I don't understand this limitation on any of the sites.

Then, I'd argue that writing iOS app in Objective C is not native because there are several layers between Obj-C and the Apple A7 cpu.

There might be more layers on Firefox OS than iOS, but I'd take more abstraction layer than write speedy "native" code any day.

This is usually how you codify a dynamic programming algorithm. Good to know that there's a name.