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

If you haven't coded serious projects in at least 5 very different languages, you likely adore one language because you just don't know better.

There is such a variation between js, perl, python, rust, C#, lisp, bash, haskell, erlang and sql that the blind spot is huge.

It's like eating hot dogs all your life and debating food merits with people that tasted japanese, indian and french food.


I’m mixing Python, C++, Java, Kotlin and shell scripting professionally. Used to work on enterprise C# project. Experimented on a hobby level with Elixir, Haskell, OCaml, Ruby, TypeScript, JS, Dart.


I'm recently enjoying F# a lot. What really sold it was partial application and absolutely bonkers type inference with gradual typing. You just write code and let type system infer the signature of the functions, only specifying the types when necessary. It's so much cleaner and I'm sorely missing it in C#.

It's a bit off-topic but if you liked Elixir it's kind of like Elixir but fast, and like OCaml but widely usable in production. It could also be familiar after Python due to mostly indentation-based scoping and not having to define signatures (except you go from something terrible and untyped to Hindley-Milner).


Python, C++, Java, Kotlin and shell scripting are all globally mutable procedural / imperative languages. Of course you'll also like JS.

Spend several years with LISP, Elixir, Haskell, OCaml, then you'd be in a better position to say you keep loving JS.

You are sticking to the same type of languages. This warps your point of view.


What an obnoxious and condescending response. They said they've used those languages. Consider that these languages have huge flaws of their own. Elixir doesn't even have a proper language server. Using niche languages does not automatically make you special on internet forums.


Elixir has two fully functional language servers and it's very far from niche, or I've been spending imaginary money for the last 9 years.

What I said still applies, the guy seems to have a familiarity bias and said nothing to show otherwise.

As for being condescending, your reply seems like a textbook example.


amen. there’s people that use haskell, ocaml, lisp… and then there’s rest of us that do actual real work :)


Oh yeah, that's not obnoxious at all. :D

Lost on your way to Reddit, I see.


you can dish it out but you can't take it, I see... :)


I said was that I believe the poster lacks the perspective to criticize certain languages. That was and still is the topic.

You are free to interpret it any flame-bait ways. I ain't biting though.

Peace.


did you actually read the post? where from his post do you get "poster lacks the perspective to criticize certain languages?"

and of course even more pertinent - which languages did he even criticize other than to point out things that are not possible in Scala/Rust (certainly not a critique, each language has its pros/cons...)


Maybe zig will become what rust is for python.

But JS needs a better compiled extension story for that to happen. The absence of a standard like wheels makes everything difficult.


I don't think that compiled extensions are a good solution for any particular task. Projects that need some code outside of JS ecosystem can compile it to WASM, project that need a lot of it should be done in that language instead.


The entire AI ecosystem, the scientific stack, the GIS crowd and 3D modeling community disagree with you.

And they went for python, not js, because of this.


You're providing examples of "project that need a lot of it should be done in that language instead". What would these projects even gain from using nodejs on backend and packing most of their business code into extensions for node?


Talk is cheap, they coded it.


I get your point, but once in a while, you get a gem like uv for python.

The fact uv is not in python means it's immune to the many bootstrapping problems the language suffers, which in itself is a huge win.

Granted, it works only because it's well engineered. The python integration is fluid, it respects standards, you never actually feels you are dealing with a separate tech.

This is rare.

Usually the experience is more something like asdf which gets 70% there then left you hanging.

However, when that works, it brings many benefits. An unconspiscious one for uv is that we now have a packaging tool compatible with pip that you can call from any other language with no need for a python runtime, and no risk of breaking if other runtimes exist and move.


That's why they are not unspecified to be optional.


Would buy. But you probably should teach a few live courses before writing it because of expert blindness. Otherwise you will miss thr mark.

Would pay for a decent remote live course intro.


Yes, is performance Pareto, or perception of performance Pareto?


In Python, contract based programming can be only be done properly with asserts:

- You can't use the type system for some constraints.

- Asserts can be stripped in production so you don't pay the price for them.

- There is not other syntax for that.

Unfortunatly, because most devs don't know about "-O" and use asserts for things you should use an Exception for, you can't use it: https://www.bitecode.dev/p/the-best-python-feature-you-canno...


Depends on the profile, when somebody talks to me like that I immediately cringe in my head and lose all respect for the person.

Probably a matter of culture too.


This seems like a very shallow way of thinking. "Losing all respect for the person" implies that you think this is NEVER an appropriate way to address someone. Phrasing a disagreement of opinion as a question of reasoning is often the best course of action.

In particular if a choice has been made and going back to reverse it has significant costs, it is important to not say anything like "We should not be doing this" or "You made a mistake." Unless there is a good of action to reverse course that is simply being rude for no reason. Even in the case where there is a good way to reverse a decision, I would rather ask for the reasoning that led to the decision than strongly state the decision is wrong. If I am working with someone I respect at all, I must entertain the thought that I am wrong and they made the right decision with good reasoning.

What would you say to a superior who made a decision that you disagree with, but don't think is worth reversing? My best guess is either nothing or something that more strongly asserts your belief, but I can't think of any better option than phrasing it as a question.


> What would you say to a superior who made a decision that you disagree with, but don't think is worth reversing?

"I don't understand ... it seems it has the consequence of ... My professional opinion in that case would be... and I would advise to... because of... Is there something I'm not seeing here?"

Benefits:

- I'm not faking it.

- I already provide a lot of information up front to limit back-and-forth. This avoids assumptions and also works better for when you WFH.

- The person knows exactly where I stand and where I want to go. It's not chit-chat, it's not politics, it's purely technical and I want to move on the issue.

- If I'm wrong, I can get told right away. If I'm right, it's factual, and we can move on to solving the problem. And if the person's ego/social status is on the line, they can just BS their way out of it, and I'll just add nothing and move on.

- The template drives the conversation enough that they only need a short answer to let us decide if it's worth reversing. And we can conclude on the price / consequence of that and move on if needed.

I'll change that depending on the person. Some people are way better than me, in that case, I'll default to asking what I'm missing because it's likely they see something I don't.

On the opposite, if it's a junior, I'll assume they get it wrong and help them to fix it (unless they can justify it).

And of course, phrasing will depend of how much intimate I am with the person. Good friends will get a playful version, uptight clients will get the more formal one.

Once you have done that several times and people know the routine and the relationship is good, you barely have to speak. You can just nod at something or raise an eyebrow, and start problem solving or get the info.

But note that I can do that also because my clients value my opinion enough, have respect for my professionalism, and also know, because of my past interactions with them, that I focus on the problem to solve rather than blaming.


> Is there something I'm not seeing here?

That's essentially the same thing. The only difference is that you're putting your uncertainty at the end and I'm putting it at the beginning. The key is to explicitly acknowledge that you recognize the possibility that you might be wrong.


Same here - whenever I see someone trying to get around giving honest feedback, and trying to frame it as "humble curiosity" instead, I immediately assume they read some "leadership" articles and are trying to apply it because they are second guessing themselves. I believe it depends a lot on the culture, but I am much more used to either keeping my mouth shut (when there is nothing on the line) or being blunt (when it matters). Either way, no sugarcoating or "being curious".


The problem with being more assertive is that there is always the possibility that you are wrong and the person you are "correcting" is right. Opening with an assertion makes it hard to save face in that case.


It's a quantum zoom: it's zoomed in and not zoomed in at the same time.


If you like this kind of things the French state geographic portal (https://www.geoportail.gouv.fr) lets you load crazy tiles like the Cassiny maps (from 1682) and the military staff map from 1820.

It's a blast, but in French only so you'll have to fiddle around a little.


In FireFox I can translate the site to English.


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

Search: