Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
throwaway313373
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
throwaway313373
2y ago
There is no secret ingredient, Yandex just put more effort into supporting languages that are spoken in ex-USSR countries, because that's the most important market for them. Other translation tools do not consider i. e. Kyrgyzstan an i
2.
▲
by
throwaway313373
2y ago
> some censorship How the hell is everyone okay with it? Why should I be "forbidden" from understanding a text written in a foreign language if it contains something inappropriate? I don't know of any translation service t
3.
▲
by
throwaway313373
2y ago
> BeOS also had 750ms preemption interval (or was it 3ms, I dont remember) 3ms vs almost a second is a pretty big difference...
4.
▲
by
throwaway313373
2y ago
I don't think that "skin in the game" means what you think it means.
5.
▲
by
throwaway313373
2y ago
Is it a violation of any of the policies?
6.
▲
by
throwaway313373
2y ago
You could probably use much smaller model for such rewriting
7.
▲
by
throwaway313373
2y ago
The most interesting idea in my opinion is biased reference counting [0]. An oversimplified explanation (and maybe wrong) of it goes like this: problem: - each object needs a reference counter, because of how memory management in Python wor
8.
▲
by
throwaway313373
2y ago
AFAIK the initial prototype called nogil was developed by a person named Sam Gross who also wrote a detailed article [0] about it. He also had a meeting with Python core. Notes from this meeting [1] by Łukasz Langa provide more high-level o
9.
▲
by
throwaway313373
2y ago
I always wondered who even decided that averaging the input is a good idea. It sounds like it makes sense at first glance, but if you think about it a little bit more it actually doesn't make any sense. The average of two inputs is bas
10.
▲
by
throwaway313373
2y ago
I think that people who suggest to "just write cleaner code" are missing the point entirely. Of course, we all are trying to write clear code. It doesn't mean that your tool should make working with less than perfect codebase
11.
▲
by
throwaway313373
2y ago
It is unclear what is the condition of automatic folding of the second level and below. If you are using "Go to..." a struct declaration or impl in Rust (or a class in other languages) it actually makes a lot of sense. If I'm
12.
▲
by
throwaway313373
2y ago
> "they care more about doing things right than delivering quickly" Is it actually supposed to be a negative review...
13.
▲
by
throwaway313373
2y ago
What does the feature discussed in TFA (chained comparisons) have to do with Python 2 vs Python now. As another commenter pointed out [0] this feature existed since 1.4 [1]. Also, I don't understand why so many people seem to be so con
14.
▲
by
throwaway313373
2y ago
"someone who writes code" is very vague. For someone who writes code primarily in Python this behavior is less surprising than the rest that you described.
15.
▲
by
throwaway313373
2y ago
It has been pointed: https://news.ycombinator.com/item?id=42038027
16.
▲
by
throwaway313373
2y ago
I've just checked [0], Rust bans such construct for booleans as well. [0] https://play.rust-lang.org/?version=stable&mode=debug&editio...
17.
▲
by
throwaway313373
2y ago
I can think of some more interesting examples when it violates intuition gained from mathematical notation. When looking at `a == b == c` we naturally assume that not only `a == b` and `b == c` but also `a == c` because equality is assumed
18.
▲
by
throwaway313373
2y ago
Rust also gives a custom error message [0] that explicitly explains that "comparison operators cannot be chained" and shows you how to rewrite the expression using `&&`. Which makes me wonder whether they came up with this
19.
▲
by
throwaway313373
2y ago
Of course, you're right, it is not possible to to share a connection pool between processes without pgbouncer. > Parent comment is talking about one connection per process with 50k processes. It is actually not clear what parent com
20.
▲
by
throwaway313373
2y ago
As I said, you can return the connection to the connection pool. From the perspective of keeping the number of open connections low it doesn't really matter if you close it or return to the pool, because in either case the connection b
21.
▲
by
throwaway313373
2y ago
If you insist on following an honor code while competing against people who are ready to take an unfair advantage of you, you lose.
22.
▲
by
throwaway313373
2y ago
Between queries in the same transaction? No Between transactions? Yes, absolutely In fact, many libraries do it automatically. For example, SQLAlchemy doc explicitly says [0]: > After the commit, the Connection object associated with tha
23.
▲
by
throwaway313373
2y ago
I think that the main issue here is not treating true/false as values but allowing them to be implicitly converted or compared to numbers with the assumption that true equals 1 and false equals 0. I think that Rust got this right. It d
24.
▲
by
throwaway313373
2y ago
This is the most important part: don't
25.
▲
by
throwaway313373
2y ago
Sounds like something that an unreasonable person would say.
26.
▲
by
throwaway313373
2y ago
But it's not a "trick", it's just a normal Python code. I don't think that anyone who main programs in Python would perceive it as some kind of cool/unusual trick and not just normal code.
27.
▲
by
throwaway313373
2y ago
To be fair, there are edge cases [0] when it does look weird. [0] https://github.com/satwikkansal/wtfpython?tab=readme-ov-file...
28.
▲
by
throwaway313373
2y ago
I don't know why didn't the candidate just explain to the interviewer what chain expressions are.
29.
▲
by
throwaway313373
2y ago
Why would you want every "frontend" keep an open connection all the time? > it doesn't matter if they are all active It does, if the connection is inactive (doesn't hold an open transaction) you should close it or ret
30.
▲
by
throwaway313373
2y ago
Why is it "shocking"? It's just an architectural decision to spawn a process per connection that Postgres made long time ago. It's a tradeoff like most decisions. Back in the days MySQL had huge issues with scaling to mu
More ›