Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

I know it's supposed to be a parody, but it hits very close to home.


Because of contact discovery and migration. The success of those apps is directly related to the fact you can instantly see all your contacts with it when it first start. Email wouldn't have the same effect because poeple don't have them saved in the contact list.

I think university should have a mandatory course where IT student go and interact with real users and have a budget to manage according to the success of their exhange. It would make those questions much less likely.


Not sure I agree. Although I’m not 100% certain of all smartphone implementations. But I definitely have emails for everyone in my addressbook/contacts list.

It’s the only thing that exists which can be anonymised properly and is static through many centralised providers.

Otherwise it’s back to usernames and the bazaar that is: does this person /actually/ have their names on telegram/skype/whatever


See second part of my comment. You are in the HN bubble.


I don't think this is true at all, maybe you are in a USA bubble? People in other parts of the world do not seem have a problem adding each other on LINE or Facebook for example without using a phone number at all. Meanwhile one friend of mine has lived in France, the UK and Germany in the last few years and I have no idea what his current phone number(s) are or what country they are from. Many acquaintances who I have not spoken to for some time have most likely moved abroad at some point and I doubt any of the phone numbers I have for them are still correct.

In my experience, for reasons like this, people do not generally bother swapping phone numbers any more.

Meanwhile, in Southeast Asia recently, I was unable to sign up for Discord because they required verification with a phone number. My local phone number was rejected because it was prepay, not a contract. I wonder how many people in that part of the world have a phone contract? Does Signal also enforce that requirement? Should access to secure comminications really be linked to one's credit history in that way?


The lack of automatic contact discovery never stopped people of looking up each other on Facebook. I don't see why messaging would be different.


Of course it did: facebook actually started by using the university contacts to propagate using a spammer strategy.

Now that it can't, it invasive use your personal information to suggest contacts.


> To me it feels like python is running as far away from simplicity as fast as possible.

In the field, Python stays mostly simple. All those stuff are optional, and they are used in this spirit.

In fact, most Python code I see out there seldom even use lambdas, comprehension lists or yield.

You gotta remember a huge part of the Python user base are not programmers, and they don't have the time to figure those things out.

That's one of the reason of Python success: it scales up, and it scales down.


The functional paradigm is a matter of taste. Python is willingly limited in its functional capabilities.

You may not like it, but it's not an error, it's a design decision.


I think it wasn’t the OP’s point to question the design process behind Python — he was mostly just reacting to the commenter above who claimed that:

> Python is a very powerful dynamic language. It lets you code with any paradigm that suits the problem you’re trying to solve. Functional, OOP, procedural, or whatever.

Which simply isn’t true (as is proven by you as well) — Python was never designed to “let you code with any paradigm that suits the problem”. It has severely limited functional and (nonexistent?) metaprogramming capabilities, so the claim might be better phrased as follows:

> Python is a very powerful dynamic language. It lets you code with any paradigm that suits the problem you’re trying to solve, as long as it’s OOP.

(Please excuse the sarcasm: I work with Python and I like it for its simplicity, good tooling and a myriad of other things, but “flexibility”, for a lack of a better word — especially compared with LISP — is not one of them.)


It's perfectly possible to be both a design decision and an error. False dichotomy, as they say :-)


Again, a programming paradigm is like code formatting rules or ide choice. It's a matter of taste. Saying one is an error is just reenacting vim vs emacs. It goes nowhere.


Most ISP put this kind of QR code on the provided "modem" in France with the default Wifi password of the device.

I love QR code. I think it should be everywhere. All legal documents and forms should have one. All supermarket bills should have one.

It's a fantastic way to transition from paper to bits.

Unfortunately most users have no idea what it is. They don't know what a URL is, so a QR code is out of the question.

Plus they don't necessarily have a QR code scanner on their devices: not all phones have one by default, most laptops definitely don't. Not to mention some QRcode readers are sometimes just the regular camera app (E.G: modern iOS), which is very confusing. And even if all that is not a problem, your QRcode scanner may not be able to understand a particular format or will read the Wifi code but just display it while it's supposed to save it as a new access point.

It's definitely not a solved problem.


Are you not concerned that QR code’s are just completely opaque URLs asking to be clicked? Do you confidently click on URLs in spam emails? Of course not since we all know URLs can point to malicious payloads. So why should we love QR code’s that could just as easily do the same.

If I’m a spammer trying to get people to click on my bogus links in my email messages, why wouldn’t I also print those same URLs as QR codes and paste them around my city with creatively enticing titles.


Do you never click URLs in emails? Of course you do, when you're confident the sender is reputable.

Parent was referencing trusted contexts: the default password printed on your wifi router, the bill a cashier just handed you for what you just bought, the legal papers you just signed, etc. The QR code just links the trusted document with trustworthy digital versions & extended content.

I'm not worried a spammer is going to get a bogus QR printed on the grocery store receipt I just received. I'm not going to scan QR codes printed & posted on subway walls for no apparent reason.


I can't imagine a qr code on a receipt being anything but tracker-infested spam.


That's how it currently is in some shops. Amazing how marketers are always ahead on such technologies.


Can confirm.

I was visiting a nature reserve where the trail opened to a resting area with some seats. A tree had a woodcut QR code on it, so I thought I'd scan it to find out more about the area.

Turns out, the QR code linked to some tracking site with a short URL. Even worse, the short URL had since been deleted, so I have no way to know the original URL it went to.


Yep, it'll definitely have a tracking code added to the URL.


> Do you never click URLs in emails? Of course you do, when you're confident the sender is reputable.

Nope. I go to the sender's URL manually and look for what it is they sent an email about.


You’re the exception that proves the rule


Exactly.


Don't most people within the HN demographic mouse over to see the link in emails?


For comparison, my phone shows me the URL that the QR code decoded to, and prompts me to confirm that I want to browse to it


Remember bitly, AMP, CDNs?

Also, as to something like a javascript exploit in a URL itself, QRs can hold a surprising amount of data, enough to max out most URL browser limits around 2,048 bytes.


At least bitly lets you look before you keep. Add a + to the end of any bitly URL to see where it goes, when it was created, and how many peole clicked it.


You've described some of the scenarios that would result in me not clicking the link. The feature works well, doesn't it.

This is functionally the same as hovering over links in emails, which is the context in which I made my comment.


Ok, explain those to my mom.


Ok but if it's a bitly link then I'm still not clicking. Just like it an email includes an obviously shortened email.


Bitly is so useful though for making usable QR links


On the desktop, especially if the Email is even slightly suspicious? Always. On mobile, it's somehow a lot more difficult and user unfriendly.


hover text and/or copy and paste into browser before hitting go.


The QR scanning app that I use displays the URL so I can check if it looks okay, but most of them are abbreviated using services like bit.ly, so that doesn't help much. You'd have to have a UI that lets the user step through several redirections, but that would probably confuse people.


You're shifting responsibility from developers to the users. If reading a QR code triggers a bank transaction, that's an issue with the QR scanner and the banking application.

Users cannot check if a domain is "ok" by looking at it. You visit websites to discover what's there. A few years ago it was common knowledge that ".to" is shady and ".com" looks more legit. Now we have more TLDs than I can count. How is someone supposed to check that with visual inspection?

The way it should go: you scan a QR code. It gets interpreted into something useful that doesn't cause harm.

"Hey this QR would cause a 5€ transaction to Jon Doe. OK?" That's something the user can decide upon. payment://jon-doe:5€ doesn't help much.

(Edit: reading your post again, I realize it might be exactly what you have in mind)


I was mostly thinking about URLs in untrusted contexts, like maybe from an ad you see on the street, that you want to screen by hand against malicious intent; not so much about things like your banking app example, which should always have some kind of confirmation anyway.


It really shouldn't matter to the browser what URL you enter. Maybe it's not the page you're looking for. But opening a website itself should cause no harm.

Just compare with today's internet advertising. Legit websites are still full of somewhat malicious ads. And users click on it - of course, since that's what a website is for.

What I'm trying to make clear is that there is no such case where QR scanners, browsers or application may consider a safe context where the user implicitly consents with malicious actions by the QR/website/...


> It really shouldn't matter to the browser what URL you enter.

In a world where browsers are vulnerable to remote code execution, and a world where users do not run the latest version of a browser, and in a world where zero days exist in browers, it absolutely does matter.


Qrafter on iOS has exactly that UI, which is why I use it.


If anyone knows of an equivalent on Android (preferably available on F-Droid), I'm all ears.


I recommend “Privacy Friendly QR Scanner” (https://github.com/SecUSo/privacy-friendly-qr-scanner) by the SECUSO group, who specialize in apps that respect user privacy.

Worked great for me on my last phone, and peace of mind knowing you aren’t being tracked.

Available to download on fdroid or the play store.

https://github.com/SecUSo


SecScanQR shows you the URL and lets you decide if you want to open it or not. It's on F-Droid. https://f-droid.org/en/packages/de.t_dankworth.secscanqr/


No more than regular url written in a paper. People write them blindly anyway, they don't know what it means nor how to read it.

But QR code are not just for URL, they can contain up to 7k, which is a lot for text and numbers. And you can have several of them, use compression, etc.


Because urls have letters & words in english that I can read and determine if the website is authentic or not as opposed to QR code that no human can read?

Have you never come across phishing scams that looked eerily authentic only to be clued in by the fake url? I can read the URL before going to the website, and unless QR codes have a step where you have to manually confirm going to the url provided by the code (most don't) then that's a security risk


Qr code readers show you the url, you have push a button to navigate to it. So it's no different than having it copied manually.

Not that it matters much for most users, as I said earlier, they blindly type url. They have no idea what it is.

You could put a warning saying "are you sure, this is going to kill your mother and steal all your money" and people would click on it if it's easy to do.


Microsoft did that research. Well, they didn't propose to kill anybody's mother but the test participants used their real bank credentials and Microsoft tested different behaviours in IE to see what would deter users from giving these credentials to a bogus site having accepted a task to log in and perform some basic operation.

Nothing.

Nothing deterred the users. Warning dialogs were clicked past, obvious problems or mismatched information was ignored. The only way to stop users from giving their credentials to bad guys was what I call Brick Wall UX. The browser has to stubbornly refuse to let you do it. Unable to complete their task the user at last gives up.

This is a teachable moment. Your users are probably not going to be smarter, better informed or more cautious at least on average than in this test.


This sounds like something which should be continuously tested, as a litmus test as to how careful people are. I don't suppose you have a link or pointed search terms for this instance?


Because urls have letters & words in english that I can read and determine if the website is authentic

You must have some super-human ability to read a computer's mind if you can grok the kind of urls that usually come in emails like https://tinyurl.com/uvc58uq


You can see what the tinyurl redirect destination URL is (value of Location response header) without also requesting that URL. Not with a typical browser configuration, but with curl or some hosted solution delivering this functionality.

Of course, if the email actually has a unique URL per recipient, then doing this gives away the fact that you interacted with the email.


Clicking a link can't infect your computer with a virus anymore. As long as any vulnerabilities in QR scanner apps are reliably patched, it should be just as safe as clicking a link. There are zero-days, but that risk exists any time you're connected to the internet anyway.

The cost and risk of putting a sticker on a wall is much greater that that of sending a spam email. Legitimate advertisers already hire people for >$0 to do that. Illegitimate ones risk personal criminal prosecution because they have to be physically present.


plenty of scanners allow you to decode a code & show the url or whatever is encoded in it without opening the link & give you options so I wouldn't be concerned at all.


Use bit.ly it's quicker ;)


FWIW, I know iOS's camera natively detects QR codes, and I believe Android does as well.

In my opinion, the ability to use the native camera app to read a QR code significantly reduces the barriers-to-read for general users


Absolutely game changing for the technology! And very convenient too


"very convenient"...

Nowadays it seems anything that can do something FOR you usually does something TO you.


They can’t be used to encode very much data though. They wouldn’t be suitable for storing documents, but could be used to store the location of a document. I was trying to be clever once and thought I could encode X.509 certificates in QR codes. Even that much data was pushing the hard limits of what they can store, and became very hard to scan (I quickly realised this wasn’t actually very clever).


7kb for a supermarket bill is plenty, and you can have several of them.

Forms and legal documents should all have an immutable official url and uuid anyway to point to their legal and administrative context.


The largest QR code in the standard, "version 40" - can only store 3 kilobytes at the lowest level of error correction and 1.2 kilobytes at the highest level [1]. And that's a pretty huge QR code [2]

My back-of-the-envelope calculations say you'd need 61 bits per line on a receipt just to encode UPC, quantity and price. So the largest QR code would only allow 19-50 lines. And that's without including data like the store name, special offers, means of payment and so on. Believe me, plenty of people buy more than 50 items in their supermarket christmas shop :)

Standardised digital receipts would be neat but, QR codes encoding the data ain't the way to go about it.

[1] https://www.qrcode.com/en/about/version.html [2] https://commons.wikimedia.org/wiki/File:Qr-code-ver-40.svg


Seems like the obvious thing would be to have the QR code contain a "receipt ID" (UUID?) in a URL.

When the QR code is scanned, the browser opens to the URL, the remote side takes your "receipt ID", and presents you with a list of all the items you purchased.

I can't imagine any decent-sized retailer isn't already maintaining records like this.


See, one of the useful properties of a paper receipt is that, once you receive it, you can be fairly confident about the ~one way you're going to lose it


Two ways. Receipts fade, sometimes very quickly.


1.2 kilobytes = 9.6 kilobits. If you need 61 bits per line, you’ve got enough bits for 157 lines. 393 lines if we go with 3 kilobytes. I think you may have used 61 bytes per line in your calculation rather than 61 bits.


I (not OP) would say bytes would be closer. The product name could be 20 characters long (20 bytes minimum)


OP was assuming the receipt would list the product UPC code rather than product name. A UPC code is 12 digits, which can be encoded in 40 bits.


it could just contain a url linking to a page with to content.


I wish we could encode PGP public keys with them, but it's still too much data.

That would be a neat way of exchanging a key.


You can definitely encode ed25519 keys to a QR code.


How big is your pgp public key? Mine is under 4K in ascii and can definitely fit in a QR code.

If you use a crypto atm it will print out your wallet’s private and sometimes public keys as QR codes.


4K is around the point where some devices will start to have issues scanning. Also, crypto wallets won’t usually give you the private key, instead they’ll give you the 12 word BIP39 seed phrase which will be around 70-80 bytes.


Gpg key fingerprints are very small though and can be used for that.


Can X.509 ceros use elliptic curve? They’d be much smaller.


Even without the key they start to look pretty dense. You can definitely fit one in a QR code, they just start to become less reliable to scan (especially on cheap devices), and they go from looking nice to looking quite ugly. Technically most X.509 certs would have been within the limitations of QR codes (though I don’t think there is an upper bound to how large they can get), but I realized it just wasn’t fit for purpose and moved on to something else.


Are you using 8 bit encoding? An alphanumeric mode QR code containing base 64 encoded data provides less capacity. In binary mode even a 4096 bit RSA secret key fits while ECC keys produce smaller codes.

The qrencode tool has an 8 bit mode but not all decoders can handle binary data. For example, my phone shows me mangled results and I can't redirect them to a file. Like structured append, it doesn't seem to have much support.

I've sent patches to ZBar improving this:

https://github.com/mchehab/zbar/pull/64

Hopefully it will make QR codes more useful for storing keys and other small files.


i think datamatrix is more suitable for x509


Yes.. I had made a form that was scanned and all the metadata for the page was stored in datamatrix at the bottom.. With a laser printer and a good scanner you can reliably put a lot of data in there...


> Not to mention some QRcode readers are sometimes just the regular camera app (E.G: modern iOS), which is very confusing.

You can use that if you wish, however there is an entirely separate and dedicated QR reader built into iOS that is accessible from control center. The icon to launch it is even a QR code which eliminates such “confusion”.


Huh, I had no idea there was a dedicated QR reader "app", since it's not a default icon (you have to add it from within Settings), and there's no actual app. But it's there!

Interesting they added that when the camera app already scans QR codes. I wonder if it's an enterprise thing for devices in the field, where companies want to prevent the camera app (no photos), but need to scan codes.


Have you been to China? QR—everywhere.


QR in China are different animals.

They are not generic QR codes, but encoded instructions to access specific in-app features in WeChat/AliPay. If you scan those special codes with generic QR readers, you get invalid URLs.

IMO this makes it even worse to use generic QR codes, because if a QR code cannot be parsed by WeChat/AliPay, most Chinese users do not know what to do with it.


Yes, that's why I know it's possible.


>All legal documents and forms should have one.

The ones you download from e-government in Turkey have QR codes. I think other e-documents have QR code too. You can validate them by using https://play.google.com/store/apps/details?id=tr.gov.turkiye...


Current Android WiFi list has a dedicated QR Code button next to it, so it should become more accessible in half a year when most people are on Android 10


This data [1] from google is a bit old (from May 2019), but shows about 10% on Android 9, and maybe a third on Android 8+; to get 50%+ (the common interpretation of most) you're looking at Android 7+, and that was released three years before the stats. Maybe, if uptake of 10 is as good as 7+, we'll see most people on Android being able to use this in 2022.

[1] https://developer.android.com/about/dashboards/


Project Trebble made a huge difference, and Android 9, which is one year old, is already at 48% market share. This is so much faster than older Android upgrades before it.

Source: https://www.androidpolice.com/2019/12/18/pornhub-does-what-g...


Stats from different places are going to show different trends. Google's stats are a lot closer to all of the Android market than PornHub's. It's unfortunate that Google is slow to update. But it might be interesting to look at trends in PornHub's data, if they provide it over multiple years.


> Unfortunately most users have no idea what it is.

In the west, yes, it's absolutely prolific in Asia though. Even the most technologically illiterate people over there know and use qr codes all the time. A huge divide.


They teach kindergarten's to use QR code where I live.


firefox preview has an embedded qrcode scanner


For url only. Qrcode are for much more than url.


You either use URL or custom app to scan Qrcode. You can't encode arbitrary data and expect universal reader being able to interpret it. And URL is actually good way to store small amounts of data, because you can launch web app to handle it and it's compatible with any device.


you probably mean URI


I'm not sure it's only for urls


It normalizes the way templates are coded and forces people to put minimal logic in their rendering.

In react, there are as many ways to do the same things as there are coders. And of course, some don't follow best practices and will put logic code in it.

Personnally I also find it easier to picture the resulting DOM structure because the stylee is forced to be declarative. Too often in react I have to look around a tag to know whats hapening, or I have to follow some nested map/filter/ternary chaining.

Very good react coders will not do that. They will use a lot of tooling and abstract formatting a lot. But they are few.


I'm not sure how it forces less logic in the render. Looking at the Svelte docs you can do this:

``` {#if invokeFunction()} <p>This function returned a truthy value!</p> {/if} ```

And with React do this:

``` { invokeFunction() && <p>This function returned a truthy value</p> } ```

and the result would be the same, a conditionally rendered string. I totally agree in the normalizing/formalizing how templates are build and the more verbose syntax in the Svelete example does make it super obvious. The in-line React example is obvious to me...but maybe that's because I've been writing js for so long.

Where I feel the cognitive overhead pain in looping. Svelete's docs say:

``` {#each collection as { vars }, i} <p key={i}> {vars} </p> {#/each}

```

For some reason, when I see this it rubs me the wrong way. I understand it...but my instinct is to just map over the collection like I would in a plain-old Node.js project.

``` { collection.map((vars, i) => <p key={i}> {vars} </p> } ```

I guess that saving a handful of keystrokes in exchange for super clearly expressing the intent may be a good tradeoff, even if my inclination is towards more terse code.


In Vue it would be:

    <p v-for="(vars, i) in collection" :key="i">
      {{ vars }}
    </p>
Instead of:

    { collection.map((vars, i) => <p key={i}> {vars} </p> }
It's easier for me to picture what the first example is going to render because it makes the markup the hero, with code inside, while the second example is making JS the hero, with markup inside.

But this example is not even touching the topic. A render function is rarely that simple. Now if you do maps, and filters, and ternary operators, and && / || pass trougth, and set several class conditionally, and pass an event and do preventDefault, etc., now you have a more real life example. And in react you'll get __a lot__ of JS, with very little markup. And you'll have either a lot of boilerplate, or a lot of dependencies to get helpers.

While in Vue you'll get mostly markup, with a little code inside. It will read from top to bottom as well. No needs to wrap stuff in arrow functions to get the event object. PreventDefault has a helper. Setting classes as well. I prefer that.


Vue's templates are great until they aren't, and then you wish you were using JSX.

The IDE tooling is worlds better with JSX as well. Vetur has.. had a rough year.


I don't have to debug my render functions much in vue because they contains little logic. Debugging is more common in JSX, it's better at solving a problem it introduces.


The second example isn’t making JS the hero, it’s making data the hero.


Which is the opposite of what you want in rendering. Ui is king here. Data has the rest of the code to shine.


Things like Hiccup and React/JSX were a breath of fresh air next to templating languages like Handlebars/Mustache/Jinja. I prefer to just write simple code instead of learning the idiosyncrasies of yet another DSL.

I'm reminded of https://gbracha.blogspot.com/2014/09/a-domain-of-shadows.htm....


In your first example, if invokeFunction() returns 0, the text "0" will be inserted into the page. 0 is falsey, so `0 && <p>Hi</p>` evaluates to 0, but 0 is a number so React pastes it into the page contents.

React has footguns like this because JavaScript expressions were not designed to be used as a templating language.


Thinking your function returns a boolean when it returns an int seems like another issue entirely, like habitually depending on implicit conversion like "==". If that's a common issue for a team, maybe it's time to look into Typescript. Seems like a very minor reason to use a whole new DSL with a whole new set of warts for all of your templating.


Depends of the template language. I prefer vues's than svelte's.


> All scripting is application development. Having variation of application lifetimes, deployment circumstances, etc., does not at all represent any difference of kind in terms of reliance on third party APIs, shared abstraction layers, or the standard library. It is all just application development.

In the same way that boiling pasta is cooking.

> I strongly disagree that these different use cases imply different requirements,

But a art major student and a haute cuisine chef have vastly different needs in the way their kitchen is setup.

It just happens that Python serve the whole spectrum of user base.

You are seeing this from the point of view of a programmer. There is a enormous quantify of Python coders that are not. They don't have an IDE. Don't know what an env var is. Are not able to install dependencies. And they chose Python because it doesn't force them to.

> e.g. for separately versioned instances of the same standard library module.

How to address it properly is a different issue, and requires indeed a debate.

> Python is not unique in this at all.

Oh, but it is. See my other comment on the matter: https://news.ycombinator.com/item?id=21898070 It's very long, don't want to write that again.

> The exact same phenomenon has happened since virtually the dawn of C programming.

No. Geographers don't casually code in C. Math teachers don't have to teach it everywhere. You cannot be productive in C after 7 days of dabbling with it. And hence there is a huge number of people that will never, ever use C, or any other language, but use Python.

I wish people saying that would accompany me on my job, going from company to company all day long to witness what is really happening outside of the HN bubble. Remember, if you are on this site, you are very far from 80% of the Python coders. In fact, if you even spell "Haskell" correctly, you are in another dimension.

No one would ever mention C after that. For many, Python is way closer to Excel.

> The same thing is true for C++, Haskell, Java, Scala and many more language ecosystems.

> It’s all just application development.

Some people produce fast food. Some prepare a pick nick. Some make a banquets for a family of 30.

It's all just cooking.

I'm sorry, no, this is a misguided conclusion.

Python is the only knife I know that is popular for almost all of this different use cases of cooking, but all this different types of cookers. It makes it a special case. A very special one.


> I install new command line utilities to use in scripts all the time, rsync, cloud storage clients, silver searcher, linting tools, many things.

> Same with Python. Virtually all data cleaning scripts I write rely on special scientific computing and structured data libraries.

This is the point of view of a programmer.

You would be baffle by the number of people that code daily in Python without ever having used the terminal even once. They don't install 3rd party libs. They don't know how. Sometime they use some, using the ones provided by a distro like Anaconda installed from their sysadmin 5 years ago. Sometimes they are using Python emmbeded in a another system and just script that. Sometimes they teach and there is no reason to even use anything else. There are so many use cases that are just not yours.

Not to mention a lot of people don't even have the right to install anything. They are in corporate env with firewall and security policies that give them an immutable setup for years.

> Yep, sounds pretty standard and sounds exactly like every other mainstream programming language I’ve ever used.

Definitely not.

There is no other language that have all the following characteristics combined:

- extreme popularity (exclude haskell, lisp, Ocaml, etc)

- very easy to learn and fast to be productive with (exclude c, c++, java, etc)

- ridiculous number of different ways it used IRL (exclude ruby, php, bash, etc)

- very heterogeneous user base (exclude JS, perl, c#, etc)

Python is used in banking, by geographers, in embedded systems, in movie pipeline. Several OS rely on it, the education system is using it everywhere, it is included as a scripting engine in strange systems...

Yes, you can find that some languages have similarities for some situations. But not all of them. The closest one in JS, and yet, it doesn't come close because most people use JS in one plateform: the browser. The other use cases are dwarfed by it.

You could argue with each point individually, but combined, it would be moot. Scripting in C/C++ is not popular. People don't regularly analyze their biological data in Javascript. It is not a common thing to make operating system core services in Java. C# is not even a blimp in Unix, or bash on Windows. Perl user base is dying. Lisp/Haskell/Ocaml are still niche languages after decades. Ruby and PHP never got out of the Web.

And yes, this put the language in a very odd position.

It definitely doesn't "sounds pretty standard and sounds exactly like every other mainstream programming language".

There is literally zero example of a similar occurrence in the history of programming.


> - very heterogeneous user base (exclude JS

Er, what?


JS is very popular and has a large user base. But it's not very heterogenous, espacially compared to Python.

The vast majority of JS coders are interested in the web. A few for apps and UI in other area thanks to react native and electron. The rest is anecdotal.

There is not an entire banking industry analyzing data with JS. Biologists and chemists do not rely on JS to make their models. JS is not the de facto solution for machine learning. GIS systems are not massively scripted in JS. The cinema industry do not include JS as a core element in their rendering pipeline. No sysadmin every said "well, I know how to provision those 300 servers, I'll make a JS script". Security experts don't reach first to JS for pentesting. apt is not coded in JS. JS is not the stuff that all students will be taught in math classes. If you have a dumped csv to download from an ftp to insert in your database every night, JS is certainly not the first tool that comes to mind.

I could go on and on.

Not saying you can't do this is JS. Not saying it never happens. It's just not popular to do it.

All those tasks match some kind of user base, with different profiles, needs, skills and constraints.


Good article considering it's so rare to see people with a decent overviow of the python user base. Most just live in their use case bubble and are, as pointed in conclusion, baffled when they discover what others do with it.

In fact, the best you are at programming, the more you are likely to ignore the diversity that exist behind other entities firewalls.


It's funny because in France, we are loosing french tech talents to the US.


From what I've heard Germany is also losing a lot of talent to the us and to Switzerland as well.

Higher salaries, lower taxes, maybe even more interesting gigs. All good reasons to take the leap.


I can confirm that. My german friend just accepted a job in Sweden. He also applied for the companies in Germany but they pay really low salaries and the companies are not that insteresting.


This could be a direct consequence coming from the import/immigration of talent into the EU. The best will leave once they see change coming and usually salaries and work culture could suffer on such changes. Also being born and raised in East Europe i can say that we don't handle too great a mix with other cultures, as US does for example.


Yep, most people will move to greener pastures, when the opportunity arises. Polish people go to UK/France/Germany; People from Romania/Ukraine move to Poland, etc.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: