Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bvrmn
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
bvrmn
6mo ago
Shameless plug: https://github.com/baverman/build123d_draft Experimental extension to make code-cadding as terse as possible.
32.
▲
by
bvrmn
7mo ago
> Who is forced to use it? Just use X11, as you said (many times) you do already. Recent versions of gnome session are compiled only with wayland support in archlinux. To change DE or distribution or use custom package is quite a stretch
33.
▲
by
bvrmn
7mo ago
I bet Fabrice could write JSAndroid which would provide no lag emulation experience.
34.
▲
by
bvrmn
7mo ago
Repairability score page[1] looks like a Lenovo advert. [1]: https://www.ifixit.com/repairability/laptop-repairability-sc...
35.
▲
by
bvrmn
7mo ago
Actually in Python you could recast (zerocopy) bytearray as other primitive C type or even any other structure using ctypes module.
36.
▲
by
bvrmn
8mo ago
Naming is atrocious indeed.
37.
▲
by
bvrmn
8mo ago
It's kinda hard to deliver value in fewer lines.
38.
▲
by
bvrmn
9mo ago
Thank you for posting it. It's the launcher I didn't know I need! My usage pattern is literally: use first desktop for often used apps and search for everything else. Samsung launcher search is quite shitty and slow and takes cons
39.
▲
by
bvrmn
9mo ago
> 2.6 One vs. Many Check-outs per Repository For practical cases `git worktree` allows to have multiple checkouts. Document marks this section as "partly disputed" with an external link. IMHO git worktrees has the same ergonomi
40.
▲
by
bvrmn
9mo ago
> there's no central King whose greed for wealth can be satisfied once. King and court and lords are the same amount of greedy bastards. The issue with kings is on another plain, what to do with power transfer to a new king. Democra
41.
▲
by
bvrmn
10mo ago
I could live with 1-indexing but a closed range array unpack (slices) is quite big toll and breaks nice intuitive invariant.
42.
▲
by
bvrmn
10mo ago
1 case: 14w * 1h -> 0.014kWh * 40p of total cost. There is nothing complex. 2 case: It's an issue with mAh markings. Battery rated in Wh has same simple math. There are no consumer issues jot solves. More over additional ~10^3 magni
43.
▲
by
bvrmn
10mo ago
It's hard to see practical strengths, especially with provided code examples. Most of tax code is stack tossing hiding core logic. Code as structure could be more conveniently expressed as language data structures as structure nowdays.
44.
▲
by
bvrmn
10mo ago
It would be great to have **kwargs as frozendict by default. It could help with caching decorators to speedup key construction. For example natural key is simply `(args, kwargs)`.
45.
▲
by
bvrmn
10mo ago
That's my point. Python has convenient and good type design with str.join ignored by other languages. For example I'm lost which abstract class to inherit in Scala to obtain mkString for my custom container.
46.
▲
by
bvrmn
10mo ago
From typing perspective there is no sense to have Container[T].join() -> str for any T.
47.
▲
by
bvrmn
10mo ago
It's funny. One can't simply write a correct C code. Even after years of practice. void strclone(const char* str, char** outCpy) { size_t len = strlen(s) + 1; *outCpy = malloc(len); memcpy(outCpy,
48.
▲
by
bvrmn
10mo ago
It bothers me that majority of languages ignores a nice python approach. `', '.join(any_str_iterable)`. Instead of supporting join for myriads of containers there is a single str method.
49.
▲
by
bvrmn
10mo ago
Tailwind utilities related to flexbox/grid solved most of layout issues for me. Usually it's flex-1/flex-none to mark dynamic/static parts and gaps to separate elements. Constraint based systems usually require more inpu
50.
▲
by
bvrmn
11mo ago
Slices and UB-explicitness are quite nice comparing to C. Makes head free to think about really important things.
51.
▲
by
bvrmn
1y ago
The issue with state you should handle it. Compare for example some iterator implementation in Java and Python. Latter needs only one method with coroutine and no state to store on object level. > the state is already enough to explain a
52.
▲
by
bvrmn
1y ago
Coroutines as a technique to implement state machines is the first things which comes to my mind. It's a more abstract and requires a way less fundamentals to know comparing to concurrency.
53.
▲
by
bvrmn
1y ago
Technically there is dataclass_transform [1]. It's an ungodly hack, I don't know how it passed PEP review. And support by type checkers is questionable. After TS python hints feels like rigid and total unsound mess. [1]: https:&#
54.
▲
by
bvrmn
1y ago
I guess you didn't work with good type system then. Look for TS, for example. How it allows to make strong typing for pydantic-like libraries in FE world. All how it allows to type routers.
55.
▲
by
bvrmn
1y ago
For me it's case insensitive LIKE.
56.
▲
by
bvrmn
1y ago
> I beg of you, just design it to work well with an LR or Packrat parser generator. For those cases where this is not an option, use Earley. So many unpleasant to use languages which follow this advise. Authors try to fight generator and
57.
▲
by
bvrmn
1y ago
If you could make a good "story by commits" I assure you: a combined single commit would be as much readable as multiple. Good story is a result of composable changes highly visible without artificial splitting. Funny thing I neve
58.
▲
by
bvrmn
1y ago
`::` is quite strange. 1) It only allows to resolve nesting conflicts for a single level. 2) Could be hard to read and could lead to reasoning mistakes. 3) Looks like an attempt to differentiate HUML from YAML somehow.
59.
▲
by
bvrmn
1y ago
I have fond memories for mc during my transition from Windows and trying to replace DOS Navigator and Far Manager with something similar. Started to use ranger a long ago though and never came back.
60.
▲
by
bvrmn
1y ago
In general case generating CLI options from app models leads to horrible CLI UX. Opposite is also true. Working with "nice" CLI options as direct app models is horrendous. You need a boundary to convert nice opts into nice types.
More ›