martinbooth

It says:

> For most web apps, the DOM remains the better choice. It gives you accessibility, responsive layouts, text selection, input handling, and countless other features for free

One example I have that made me excited for this feature is the free recipe manager website I run.

Many of the paid-for competitors give users the ability to import unstructured recipe data these days from sites like instagram or at least text-only websites.

I can't afford to offer this as a feature since my website has no advertising and I just pay for it out of pocket, but it's an incredibly easy feature to add if you have the money to pay for tokens.

If I could use a local llm to do it though that runs in the person's own browser then I think it would definitely be valuable.

That said, I'm not sure the state of local llms provides a good enough experience yet (small models and slow) but that doesn't mean that in the future it might not be useful.

The propsosed apis do work for this purpose, albeit more slowly and lower quality

Why do you think this is madness? FB doesn't use git for these monorepos, so that's not really relevant, but I don't understand why you think that it's better to break a repo up because the SCM can't handle the size vs fixing the SCM so it can handle the size. I work for meta (nothing to do with the teams working on this though) and I can assure you people have considered the tradeoffs of breaking repos up just to accommodate existing SCMs vs improving the SCMs.. I think if you believe improving the SCM instead of breaking up the code is madness you should probably provide a bit more of a justification

The questions are designed to allow an interviewer to get as much signal in the 45 minutes spent in the interview.. that's why they're contrived rather than your typical piece of work. They're not designed to test you on something you would never encounter though. If a company is asking these kinds of questions and the job only ever requires dealing with npm packages that shields the engineer from this complexity then they shouldn't be doing that in my opinion. But most of the companies asking these questions are in the business of building software that requires this lower-level knowledge

I conduct interviews for Facebook and we do not discriminate on age. I assume the recruiter just got the impression you really didn’t want to interview with us. I only do the coding interviews but every piece of interview feedback I write is focused on the same criteria and that definitely does not consider age. We don’t even refer to the gender of an applicant in the feedback, and comments on an applicants age would be a quick way for me to get dropped from the interviewer pool.

This is the correct explanation (thank you) There’s no intention to hide the fact that certain links are blocked. The bug is that the status of failed message sends (not limited to blocked links) only shows an exclamation mark against the last message on web.

This was the result of a lawsuit.. getty images if I remember correctly

At the company I work for UI accessibility issues are automatic high priority bugs. You'll be an asset (as a frontend developer) to any company that values accessibility (and I'm certain that many do).

Contrary to your concerns, I think that being visually impaired and being a frontend developer will most likely open up opportunities rather than close them down.

In firefox it skips one letter at a time and maybe that is the intended behaviour, but it doesn't seem consistent with what I'd expect from a WYSIWYG editor.

I'd expect there to be 2 positions between the "e" and the "t" that the cursor would stop at so I can either insert text with the formatting of "one" or "two"

There are lots of positive comments in this thread in support of this approach and I think it's great when anyone challenges the status quo.

It is more common these days than it was for websites to support multiple styles/layouts. Whether that's because they're responsive or because they allow you to enable dark mode or because they support rtl layouts. Class names such as text-dark-soft or align-right will be misleading if text-dark-soft ends up closer to white and align-right is left aligned as a website is evolved to support these features.

Not a criticism of this approach; this is easily fixed by using names such as text-emphasized-soft or align-start (for example), just pointing out the examples in this article could be lead to problems

CSS variables can also be used to encourage picking colors or padding/margin from a curated list. The approach in this article is not required to solve that problem

Distributing an altered binary to specific targets should be impossible as WhatsApp don't control the distribution, Apple and Google do. They would also have to be complicit too for a targeted attack to be feasible. By having to distribute the same binary to everyone it is much harder to conceal a backdoor

I think the interviewer may have been a bit standoffish because he/she was expecting you to work out how to reverse a linked list rather than memorizing the algorithm.

My CS degree only taught me what a linked list is, not how to reverse one.

It's not a great question to ask because it's such a common one and many people will have learned an algorithm from a text book, but if you haven't memorized the solution it's simple enough to understand the requirements yet difficult enough to work out that you can get a good amount of insight into how a job applicant can solve rather than memorize problems.

After all, being able to separate candidates who can solve unseen problems from those who can't is one of the goals of interviews

I'm pretty sure you can. They're building a wallet, but it's not the only one. It's also separate to the rest of Facebook but likely would integrate with it well

Reasonml is just an alternative syntax for ocaml so you can definitely use it for IO.

It's bucklescript that is an alternative backend for the ocaml compiler which allows you to output js, but you don't need to use it

One reason to avoid imperial units is that people seem to be generally unsure if they're even using them! I might be wrong, but you're probably more familiar with the US system rather than imperial units (given you said you're american). Did you know there are 20 fluid ounces in a pint?

Yes.. and just like trying to get out of Ikea

The fact that the generated javascript doesn't look as neat is a pretty poor argument. Does the author avoid other language features that get "lowered" (http://ericlippert.com/2014/04/28/lowering-in-language-desig...) into less elegant code as part of the execution?

In time, we'll not see this code as it'll all happen within the javascript engines, but all features of javascript are still abstractions over lower level code.

How about writing a loop over asynchronous functions? Now that is unpleasant to look at, and most examples I've seen use recursion which is pretty limiting.

That is one of the best reasons to embrace async/await