Andi

I don't like it. I would just attach a part of a silicone baking form to the front of the body. This can be undone at any time.

Solution: Just use a firewall to block all remote requests.

It always gives me exactly 16 (or less) images. So this cannot be very reliable because there are more results. Proof: Add a space anwhere to your search string in the form and hit enter again, then some new results are mixed in.

This is how I solve this problem on my Samsung Galaxy S22: make a screenshot, then you are able to select text in the builtin Gallery app via instant OCR. Works surprisingly well. I needed some time to find this feature out.

I am missing an archive of old versions, so I can run it on Mac OS 10.14.

May take some weeks.

A compound word splitter in JS that splits up words of different (esp. Germanic) languages down to simplexes reliably based on a dictionary, including Segmenter API and SQLite FTS connector. Works very reliably by internally using statistics for known compound words, too, and a stemmer.

This isn't even alpha: Vector simplifications look cruel, especially on vector tile edges, and my Macbook Pro 2012's fan starts spinning.

The website is not usable. The cookie dialogue is shown again and again.

Haley Nahman failed to talk about the ACTORS and how they act; the word "actor"/"actress" appears 0 times in this article. Just compare those boring faces with the personalities of former decades!

I'm using this now for years on my Mac, and due to the great configurability I prefer it to the builtin mode.

Thank you!

"451: Unavailable due to legal reasons We recognize you are attempting to access this website from a country belonging to the European Economic Area (EEA) including the EU which enforces the General Data Protection Regulation (GDPR) and therefore access cannot be granted at this time. For any issues, contact info@franklinnews.org or call (847) 497-5230."

Which idiot is publishing this site?

"... focus on longevity, portability, and privacy." - "Sign in or register."

That must be a joke.

Does not work offline! No choice for me.

For stuff like this, you use schema.js.

Even better http://www.google.com/trends/?q=facebook,+google&ctab=0&...

That's it, the developer has defined the pointing position for every photo manually.

What is the point about this beyond showing pictures where the finger is next to my cursor? (Why is this popular?) It's not more interesting than a circumference search. You could implement that with a simple rtree.

Better you don't work with those people. I don't want to blame you for their lack of knowledge. But if you want to do them (and you and your project) some good, order them to learn JavaScript thoroughly (which includes the unexpected but regular features that deviate from other languages and the common pitfalls), and then go back to CS! CS inherits from JS and makes no sense without it and it fixes some pitfalls but just the ones that you can fix with the constraints and additions of a new grammar. This is not the hard path but the only path to CS.

We have learned JS, probably you forgot that you need to know it to learn CS?

This is not necessary since you usually add the CS version to your dev dependencies (package.json). That should be enough. The resulting JS should not show any reference to CS at all.

+1 (and substack is talking)

Stop wasting your time by rewriting existing JavaScript implementations in other languages that compile to JavaScript!

I use CoffeeScript in nearly all my JS packages now, and I like it a lot. But I do not like how many people use it. I use only a subset of the features. The most important aspects are: short function syntax, implicit vars, short object syntax, function binding to this, @. I always use brackets when calling functions, because you need to use them anyway, when you do not pass any arguments. Omitting brackets makes CS nearly unreadable. CoffeeScript is a big win for whatever I am doing. The resulting JavaScript is more stable since CS removes the possibility of a lot of flaws and giving developers the best parts of JS. On the other hand, you still need clear and constraining guidelines to manage complex projects. But you need that in any language and framework. It's not just a necessity in JS development. Thank you, Jeremy. It pays off!

Why do we need ebay, Yahoo, LinkedIn logos on the front page?

The question should be: How good is this first line of code and for how long will it stay?

PS: I have never played MMORPGs. Did I miss anything?

This is a very important article. Today, many people don't know anymore what well-spent time is. Distractions are everywhere around us ... but if you overcome them you are probably still on the wrong path. Everybody gets in this trap. One must learn and try to get out. Often, a conservative view combined with a high degree of openness is the only way to survive in this jungle of attention and still leave a trace in the dynamic space of tech.

I appreciate the work that was invested in this book. Thumbs up!

But:

"The aim of this document is to get you started with developing applications for Node.js, ..."

I never develop applications for node.js but instead with node.js. Yes, some people in the community seem to do the first, but serious projects are my goal.

I came across contracts some time ago and found it very appealing and inspiring, but for all my professional projects I am successfully using my own library schema.js ( https://github.com/akidee/schema.js ) - you can use it in pure JavaScript, too. (Usually I do not validate forms on the client-side, since the data must be validated on the server-side anyway. And with schema.js, you can add custom localized error messages.) Furthermore, schema.js has several modes that allow tolerant adaptation of values, so that they can be casted. "5", for example, is casted to 5. But you can switch to strict validation mode as well. You can do everything, that contracts allows, with schema.js, too. The best is that, with JSON schema, 1) you define secure validations, since with the default properties you do not forget important constraints, and 2) you do not need to test your validators any more. Conclusion: I agree that such features must make it to the core of a language. Probably you can find some useful ideas in JSON schema and schema.js. I found the JSON vocabulary to be very useful to validate JS data.