BiteCode_dev

Why something so strong and not melatonin?

Real question, never tried any.

Specifically, whitelisting the URL for the bot protection, but not the cache, so that you are still somewhat protected against adversarial use.

Cloudflare is a fantastic service with an unmatched value proposition, but it's unfortunately slowly killing web privacy, with 1000s paper cuts.

Another problem is "resist fingerprinting" prevents some canvas processing, and many websites like bluesky, linked in or substack uses canvas to handle image upload, so your images appear to be stripes of pixel.

Then you have mobile apps that just don't run if you don't have a google account, like chatgpt's native app.

I understand why people give up, trying to fight for your privacy is an uphill battle with no end in sight.

Sometimes in the middle of the sentence, I write True or None, out of habit.

This is illegal in Europe, since you can't add somebody to a list without their consent.

As usual, I know it's trendy to say on HN the EU is killing innovation with all the regulations, and there is truth to that, but there is also great customer protection, which seems constantly violated in the US.

So yes, in the US, companies can flourish, but it seems the consumers are second-class citizens compared to companies.

That's why it's nice to have both: eventually, EU regulations leak out to the rest of the world, and the US innovations reach us.

We pay the price by having a weaker economy, they pay the price by having less dignity in their life, but there is eventually balance.

That's lovely to hear.

It's great hearing it in general, but given the HN community is picky, it feels even better.

yeah sorry mb, french comming out

IPython is huge: 15,5 Mo without any extras.

Python is 150mo. Hard to justify that 10% of the lines of code, source of bugs and maintenance only go to the shell.

Sure, the statistical method matters, but I think it's missing the forest for the tree.

Any metric will differ: bpm, sleep phases, body temp, etc.

Because those devices are not super accurate, and the context you wear them in doesn't allow them to be anyway.

If you were to do a respiratory polygraph with proper medical equipment you'll find different values from your Apple Watch or Oura ring for the times you wake up. But you'll also notice a gap between getting the values at home and in a hospital, because in the hospital the nurses will check your equipment setup.

Those devices are great to give you a big picture, follow general trends and understand your own body. That's it.

"On diraît" est utilisé par les enfants de 6 ans pour parler de jouer un rôle, mais pas vraiment par les adultes pour reporter un commérage.

BS (Baliverne Saugrenue)!

La tournure correcte, "voudrait" n'est en pratique que très peu utilisée pour le témoignage indirect au quotidien.

"Il paraît qu'on a voulu te faire croire que ce genre de phrase n'est employée que dans des œuvres littéraires et télévisuelles" est beaucoup plus réaliste.

Indicatif + participe passé, ou imparfait. Le conditionnel est surtout utilisé pour l'hypothétique non lié aux ragots et encore, par des gens comme dans ce thread qui se soucient de leur language.

Par contre, au journal de 20h: "on dit dans les milieux autorisés qu'un accord secret aurait été signé" est tout à fait courant.

Note that French does have a tense for gossip.

You can say: julie aurait couché avec pierre hier, meaning julie allegedly selpt with pierre yesterday.

But it's not a cultural thing to use it outside of tv or books.

And it was very condescending as well, like explaining to you that the sky is blue while you were debatting of the weather implications of the cloud shapes.

Haven'y tested, is it blocking youtube ads?

Every companies have linux servers with crazy uptimes.

My server never crash, my linux desktop do.

I assume they don't put BSD on their client's laptop.

TypedDict features are nice, but the syntax to declare it is aweful

Have an optional one is nice for python. Would suck to be forced to use it all the time.

I do appreciate the modern features a lot personally, and the fact they have been added without breaking the world. Interpolation, spreading, map and arrow functions are a huge usability boon. Plus I'm glad I can use classes and forget that prototypes ever existed.

But I train beginners in JS and boy do I have to keep them in check. You blink and they shoot their foot, give the pieces to a dog that bite them then give them rabbies.

I think what saves JS, like Python, is that despite the modern complexity, you can start to be productive in a few days with just the essentials and learn the rest with a smooth curve, slowly as you progress.

Well, all the people that used JS 15 years ago followed Douglas Crockford advice very much to heart.

Yes, but when "the good parts" came out, half of this list was already true.

There is a reason we ignore a good chunk of the language to be productive with it.

Javascript is not simple AT ALL.

It has 3 ways to declare functions, multiple variations on arrow functions syntax, a weird prototyping inheritance system, objects you can create out of "new" on functions, object literals that can act an pseudo-classes, classes, decorators, for-i loop + maps + filter + for-in loop (with hasOwn) + forEach, async / await + promises and an invisible but always-on event loop, objects proxies, counter-intuitive array and mapping manipulations, lots of different ways to create said arrays and mappings, very rich destructuring, so many weirdnesses on parameter handling, multiple ways to do imports that don't work in all contexts, exports, string concatenation + string interpolation, no integer (but NaN), a "strict mode", two versions of comparison operators, a dangerous "with" keyword, undefined vs null, generators, sparse arrays, sets...

It also has complex rules for:

- scoping (plus global variables by default and hoisting)

- "this" values (and manual binding)

- type coercion (destroying commutativity!)

- semi-column automatic insertion

- "typeof" resolution

On top of that, you execute it in various different implementations and contexts: several browser engines and nodejs at least, with or without the DOM, in or out web workers, and potentially with WASM.

There are various versions of the ECMA standard that changes the features you have access to, unless you use a transpiler. But we don't even touch the ecosystem since it's about the language. There would be too much to say anyway.

There are only two reasons to believe JS is simple: you know too much about it, or you don't know enough.

I read both and the style is tedious, especially the dialogues, and I can only assume it's a translation thing.

WASM is a child of the browser community and built on top of existing infra.

Java was an outsider trying to get in.

The difference is not in the nature of things, but rather who championed it.

And Aurora is a thing.

Given apple was part of PRISM and, you only pay premium for the pr.

Yes, first boosts, then a few gets then a few events that cascade. It's nice.

Which means offline htmx is possible, althought I wouldn't love to maintain that.

"We don't break userspace"

I follow this: https://www.bitecode.dev/p/installing-python-the-bare-minimu...

Which is mostly latest_major - 1, adjusted to production constraints, obviously. And play with latest for fun.

I stopped using latest even for non serious projects, the ecosystem really needs time to catch up.