Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
seba_dos1
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
121.
▲
by
seba_dos1
3mo ago
Is this some kind of Pavlov's dog reaction? That's not what my comment was about, and even if it was it wouldn't make any sense anyway as KWin had good results in these measurements.
122.
▲
by
seba_dos1
3mo ago
Even the simplest 3-wire cable with nothing but wires in it will handle 45W charging already, which is enough to power my laptop. It needs to be physically broken to not work. If it doesn't, it's usually the device's fault. T
123.
▲
by
seba_dos1
3mo ago
Usually they won't charge because they're not actually USB-C devices but are just broken and only pretend to be one (mostly due to missing resistors on CC lines, but there are other ways a device can be non-compliant too).
124.
▲
by
seba_dos1
3mo ago
Nor was Qt in its first versions, but how is this adding value to the conversation? Both of them were first-class in Maemo 5 and that's when the developers were clearly being attracted to the platform which is what I was talking about
125.
▲
by
seba_dos1
3mo ago
Nope, at least in Play Store it's because of how Google chooses to run their store. Google is the middleman between two sides of the transaction and its the developer that actually sells these apps, while Valve is one of the sides of t
126.
▲
by
seba_dos1
3mo ago
There's no such thing as "Wayland input latency". It's just a word salad, akin to "HTTP animation smoothness". The post is measuring Xorg vs. KWin (and also XWayland), other implementations of either X11 or Way
127.
▲
by
seba_dos1
3mo ago
Never claimed it was.
128.
▲
by
seba_dos1
3mo ago
So you do just want to complain and simply choose to ignore what I mention about how Git UX makes sure the user has everything they need to avoid these pitfalls. OK, I'm afraid this is just wasting everyone's time. I'm not ex
129.
▲
by
seba_dos1
3mo ago
If the assumption was wrong, then your first comment was pretty much useless, and the second one didn't help either as it just describes doing things carelessly and without proper understanding. So if that reading of it is wrong, then
130.
▲
by
seba_dos1
3mo ago
Also, files don't have to be text-based at all to version them with Git. When you're versioning things for your own sake, there's often not much difference between keeping text and binary files there, as it's not like yo
131.
▲
by
seba_dos1
3mo ago
Had you actually read what I wrote, you would rather summarize it as "Git is showing exactly what's going to happen when you attempt to do it, all you have to do to make is pleasant is to not ignore it". Reading things requir
132.
▲
by
seba_dos1
3mo ago
Check out "man git-bisect".
133.
▲
by
seba_dos1
3mo ago
It won't result in the third graph on its own as E isn't reachable from D, but it could if you first merged D and E together and then used --update-refs with --rebase-merges. You could then just discard the merged branch and onl
134.
▲
by
seba_dos1
3mo ago
Of course we do and it helps tremendously when the graph is reasonable.
135.
▲
by
seba_dos1
3mo ago
These aren't troubles of someone who understands. If anyone else reading this has these kinds of troubles too - don't worry, understanding abstractions takes time and effort, you'll get there eventually (not if you'll ke
136.
▲
by
seba_dos1
3mo ago
Remotes aren't equal either. Sometimes the remote is my other machine, sometimes it's a fork on a forge used for producing CI artifacts. It's a good rule of thumb to consider shared branches to be append-only, but not every r
137.
▲
by
seba_dos1
3mo ago
There's nothing "backwards" in "rebase point of view". It's just automated cherry-picking - it's like applying patches, it's as forwards as it gets. People who think it's "backwards" us
138.
▲
by
seba_dos1
3mo ago
Commit graph is just a data structure. Sometimes it represents a "history", sometimes other things. Personally, I like it when project's repository represents the history of the project rather than the history of random thing
139.
▲
by
seba_dos1
3mo ago
Such as? When you merge a commit in that changed a file that has been already changed since the common ancestor, Git runs a tool of your choice on this file. If the tool fails, it marks the file as needing a merge and doesn't let you c
140.
▲
by
seba_dos1
3mo ago
They had no developers familiar with these Microsoft APIs as Windows Phone was starting from scratch with new APIs that were incompatible with neither Win32 nor WinCE/Windows Mobile. The only thing that could save them that they were b
141.
▲
by
seba_dos1
3mo ago
> We were so close to having literal plain Linux phones. We had that and we still do. Back in 2008 I was wondering whether I should spend my first-earned money on the first Android phone (HTC Dream, aka T1) or a "plain Linux phone&q
142.
▲
by
seba_dos1
3mo ago
Microsoft was a horrible bet in that regard. Maemo was a natural development platform for many products (just straight out of my head: Mozilla, VMware and Rovio have all chosen it organically), to the point where there was plenty of notable
143.
▲
by
seba_dos1
3mo ago
Yeah, you just have spinners that keep refreshing the page and spinning when you're using Firefox or a mobile device that's neither on Android nor iOS. Potato potato.
144.
▲
by
seba_dos1
3mo ago
It should be acknowledged, yes, but not while failing to mention that it mostly applies to the genre of competitive shooters. "Generally don't run" doesn't apply to pretty much anything else, where a statement closer to
145.
▲
by
seba_dos1
3mo ago
...and yet out of 280 multiplayer games in my library 200 are marked as Deck Verified or Playable (and most of the rest has no rating available). Also, looks like all of your examples are from a single particular niche.
146.
▲
by
seba_dos1
3mo ago
> Multiplayer games generally don't. "generally" is doing a lot of work in that sentence.
147.
▲
by
seba_dos1
3mo ago
You can.
148.
▲
by
seba_dos1
3mo ago
Your response was unwarranted. I never said anything that would suggest that most of these are phones. Some of these 2/3 are, even if they're in the minority.
149.
▲
by
seba_dos1
3mo ago
Nobody was saying anything about x86_64 being the vast majority of Waydroid installs or not but you, so not sure what's your point. Read my first comment again.
150.
▲
by
seba_dos1
3mo ago
To get to 2/3 of US installs, you have to sum all this stuff up including waydroid_arm64.
More ›