Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
zvrba
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
91.
▲
by
zvrba
5y ago
It's not whataboutism, it's pointing out that Microsoft is not the only actor using such tactics. Everyone should be treated the same.
92.
▲
by
zvrba
5y ago
Really? What does Google deserve when it nags me about switching to chrome whenever I use any of their pages from a browser that's not chrome?
93.
▲
by
zvrba
5y ago
> I can't read C# Not much different than C++... > Do you generate the sorting network at compile time No, except for power of two sizes up to 32. I experimented with run-time code generation (and compilation) for given sizes, bu
94.
▲
by
zvrba
5y ago
So for I while I've been fascinated with sorting networks because some of them are SIMD-friendly, and also how'd they perform against "traditional" sorting algorithms. The code linked to is an experiment in both evaluati
95.
▲
Show HN: Fast(er) Sorting with Sorting Networks
(github.com)
28 points
by
zvrba
5y ago
|
4 comments
96.
▲
by
zvrba
5y ago
> Nowadays C++ gets lost discussing language minutiae that it isn't as much fun as it used to be. Yeah, I agree. C++ is no longer fun at all.
97.
▲
by
zvrba
5y ago
Someone would disagree (though in context of C++): http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2018/p136... Perhaps it's easier to address the problems in a managed environment and
98.
▲
by
zvrba
5y ago
> You think an English word might use either sound based on the sounds that surround it? I don't know. > does a minimal pair exist that distinguishes Đ from DŽ Yes. Đak - DŽak (pupil / bag). The latter is though archaic and
99.
▲
by
zvrba
5y ago
Native croatian speaker. This is how I'd answer the question: Đ - angel ("soft", tip of the tongue) DŽ - jeans ("hard", middle)
100.
▲
A library design for programming with effects and handlers in C#
(github.com)
3 points
by
zvrba
5y ago
|
0 comments
101.
▲
by
zvrba
5y ago
I like the article, though... the problems it illustrates with effects are usually solved by DI/IoC containers. It even says so: > Effect handlers let us decouple the program logic from its concrete effect implementations without to
102.
▲
by
zvrba
5y ago
And sarcastically side-stepping the CoI issue.
103.
▲
by
zvrba
5y ago
Oh btw, there was no conflict of interest from your side? _Your_ company did not want to follow the maturity scale, so you made an effort to shoot the proposal down... How does that make you better than Microsoft? As for customers... there
104.
▲
by
zvrba
5y ago
I've seen your other (earlier) posts about .net ecosystem and... I'm sorry, but if the said maturity scale would exclude projects like the ones you're bragging about, it would only be good, for it would reduce the amount of j
105.
▲
by
zvrba
5y ago
> Project Maturity was a pilot including "maturity profiles," designed to improve software quality. The project was abandoned shortly after its introduction after community members complained that it was over-reaching, So "
106.
▲
by
zvrba
5y ago
The QueueProcessor example could have been written using channels, which expose async APIs. Otherwise, as others have commented, I despise how async/await is "95% done". The remaining 5% will come to bite haunt you and the do
107.
▲
by
zvrba
5y ago
> If our first choice for a server goes offline, we simply move the key to the second server in the list (which becomes our new first choice). It doesn't make sense: how do you move the keys from an offline server? The pictures in t
108.
▲
by
zvrba
5y ago
> So, if I understand your proposal correctly, You understand it correctly. > if now some dependency of Foo would change drastically The most frequent "drastic change" being writing new code and fixing bugs. It's extrem
109.
▲
by
zvrba
5y ago
> is a tricky situation: would it be really handled incorrectly? Depends. You can't know in a situation like try { DoA(); DoB(); } catch (SomethingEx e) { ... } If previously only DoB could throw SomethingEx
110.
▲
by
zvrba
5y ago
> it bubbles up past the existing handlers Unless the method 1) throws an exception which it should not have according to its declarative contract (annotations in Java, attributes in C#), and 2) it gets (erroneously) handled by an interm
111.
▲
by
zvrba
5y ago
> Where you handle exceptions has nothing to do with where they are thrown. Funny you say this, when it's demonstrably NOT the case: a throwing method NOT wrapped in a try/catch will NOT have its exceptions handled at the call
112.
▲
by
zvrba
5y ago
Not if you have user-defined value types (soon coming to Java).
113.
▲
by
zvrba
5y ago
That'd be cool. It just occurred to me that I could probably do the same with attributes and DynamicProxy for C#. And also implement additional checks like "IF X is thrown, its properties must satisfiy some constraints.". (I
114.
▲
by
zvrba
5y ago
> If base exception type had a single property, something like "CanRetry", "Can retry" _WHAT_? This can work if you meticulously rewrap low-level exceptions into higher-level ones that reflect the high-level operation
115.
▲
by
zvrba
5y ago
It has nothing to do with "exceptionality". It has to do with the method not being able to fulfill its contract. Rust's returning `Result<>` is a _different contract_.
116.
▲
by
zvrba
5y ago
> Note that in Kotlin the return type is `Int?`, not `Int`. How does that fare with unnecessary boxing of primitives?
117.
▲
by
zvrba
5y ago
> You're not really disagreeing it seems. The author wrote "stop the program". I took it to mean literally: stop the program, i.e., exit immediately, i.e., crash. That's not acceptable in long-running "service&qu
118.
▲
by
zvrba
5y ago
I did in the original post, and that's why I used C++ as example instead of Java. A method declares `throws X, Y, Z` and _runtime_ checks that no other exception escapes. No source changes needed if you add W to the list. And if some o
119.
▲
by
zvrba
5y ago
Yes. What I'm thinking of are _not_ checked exceptions, at least not at compile-time.
120.
▲
by
zvrba
5y ago
> For example, Java's parseInt [1] throws a NumberFormatException if the string can't be parsed. IMHO this is terrible design. It's unergonomical design, but it's the _correct_ design: the method is declared to return
More ›