![](https://programming.dev/pictrs/image/15c9c78d-2924-41e6-b392-0dc0657ff24e.jpeg)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
I’m not seeing anything in the data collected that I wouldn’t want to be sent if the app crashed.
I’m not seeing anything in the data collected that I wouldn’t want to be sent if the app crashed.
Presenting: an excerpt from my lua windows management script:
-- Exists because lua doesn't have a round function. WAT?!
function round(num)
return math.floor(num + 0.5)
end
Yeah, not a fan.
It seemed pretty clear to me that the article states that css is doing it’s job and it’s actually fonts that are the problem
Eh, it’s the same on the Android side of the fence. There are big and small features that Google has been comically slow to crib from iOS.
I’ve definitely said “fucking finally” to things like overflow scrolling animations,
Those things like overflow scrolling, keyboard peak, etc… were only held back because Apple would patent it prevent it from being put into Android and would file frivolous lawsuits against other phone manufacturers to try and get them not to use them, even when some android variants already had it built in before apple patented it in the first place. (I still facepalm at apple trying to sue others over a rounded rectangle shaped phone)
And those patents lawsuits only stopped because other phone companies called bullshit and started threatening apple with their own patents.
and the “wild” idea that users should get 5+ of major OS releases.
TL;DR on this point: not much of an issue anymore.
This isn’t an android/iOS thing, it’s a manufacturer thing. If a chip isn’t supported by it’s manufacturer, then no software on it can be supported. Different manufacturers had different support windows, but Qualcomm became notorious for making chips, then only supporting them for 2 years so they could sell a new “supported” one (and watch the money roll in). Once they saw other the larger players getting pissed off and poking around with the idea of making their own chips, Qualcomm quickly decided that they could support their chips for longer. Now they have to since both Google and Samsung have made public promises for 5-7 year support cycles. Of course, that hasn’t stopped other phones from already reaching 7 years of official support before. (A notable example being Fairphone 2 who used a Qualcomm chip while they were still in their shitty behaviour phase and managed to support it for 7 years, 2 years Qualcomm support then 5 years of their own support despite Qualcomm.)
Also, when Google was pissed at Qualcomm they decided to start modularising their OS and pulling chunks out of it out of needing direct hardware support. This means that even if chip support were to stop, it would only affect the background / lowest-level-invisible-to-the-user parts of the OS, and all the user visible parts of the OS could be updated independently (starting with Project Treble, and going all out with Project Mainline). This basically means that entire chunks of the OS can be updated the same way an app can be, early 2010 Qualcomm companies be damned.
This also has the weird thing of android not really being a “version” per se, one phone might have different components of Android 10/11/12/13/14/etc… running at the same time. The components themselves have their own versions.
Windows 95, 98, 2000, XP and 7 are generally regarded as having great UIs.
Of course, we know what happened later:
You mean a whole different window at the OS level?
Yes, that way I could switch between windows in a single shortcut, or even place them side by side so I can see both at the same time with other shortcuts.
That’s just a way inferior hack to the way vim does it by default.
Can you explain this more?
Why wouldn’t you want window management to be managed by the window manager?
Have you considered the Required<T>
generic?
https://www.typescriptlang.org/docs/handbook/utility-types.html#requiredtype
I’m assuming for your example that only one tab is shown at a time?
In that case, you can do that in vscode, the only difference is the semantics of what is considered a “window”, and what is considered a “tab”.
To do this in vscode:
Have one window with four panes, and another window with three panes:
Window 1
┌──────────┬──────────┐
│ │ │
│ Pane 1 │ Pane 2 │
│ │ │
├──────────┼──────────┤
│ │ │
│ Pane 3 │ Pane 4 │
│ │ │
└──────────┴──────────┘
Window 2
┌──────────┬──────────┐
│ │ │
│ Pane 1 │ Pane 2 │
│ │ │
├──────────┴──────────┤
│ │
│ Pane 3 │
│ │
└─────────────────────┘
You can then switch between your windows (or “tabs” in your example) by keyboard shortcut.
In vscode, you can make the Panes different files, or even different views of the same file.
For anyone downvoting this who didn’t understand the reference:
Russia is saying that they’re the ones shooting down their own planes, because they don’t want to admit that Ukraine has the capability to shoot down their planes.
What do you mean by:
There is no way to split a tab into windows in VSCode.
Do you mean, drag a tab out of a window to create a new window? Because if so, you can do that in vscode.
How would they know a release date if they haven’t finished making it yet?
You can take the contents of a C file, put it into a C++ file and there’s an 80% chance it will work without modification, and 15% of the incompatibility will be just sticking a type on your pointer instead of using void pointers (untyped pointers), or in newer code switching the restrict keyword for one of C++'s newer pointers.
You can’t do that between JS and Java.
Space-f lets you open a file in the current workspace, and :open /path always let’s you open any file on the computer
Is this a file tree, or just a fuzzy finder?
Fuzzy finders aren’t a substitute for a file tree picker. They’re only great, until you don’t know the name of a file, or until you need to know of a file’s existence in the first place.
I remember being really interested in Helix when it came out, but it didn’t have a built-in file picker.
Is this still an issue for users? Is there a built-in solution, or a usermade solution to this?
Also, is there plugin support?
I can’t use an editor without rainbow indent/brackets, without them code just takes too long to read that it becomes frustrating.
1 hour of planning can save 10 hours of work.
1 hour of research can save 10 hours of planning.
Some small nits to fix:
C has it’s own undefined behavior.
JS has confusing behavior, not undefined behavior. Its specs are well defined and backwards compatible to a fault, making some things unintuitive and harder to learn if you don’t learn the history of the language.
Problems with both should be avoided by learning and using standard practices. (Don’t pretend C is object oriented, always use ===
instead of ==
in js, etc…)
In complete agreement:
Your question:
what things did the LHC discover that have real practical applications right now other than validating some hypothesis
Is really multiple questions:
Is doing fundamental research with no application in mind useful?
Has the LHC led to practical applications usable today
The answer to question 1 is yes.
There’s different types of research programs made to target different goals. Some aim for short or medium term applications, and others are just pure fundamental research.
Just because pure research doesn’t have an application in mind, doesn’t mean it’s not useful. The application isn’t the goal, the expansion of our knowledge base is. Everyone who ever thought up of an application for something did so based on their own knowledge base. If the knowledge base never expands, then we run out of applications to think up. This is why pure research is useful.
And all of history supports this:
The answer to question 2 is also yes:
The obvious ones are:
you have to fix the indentation because if not then the document won’t work or mean something completely different
Whitespace has no meaning in json. You can indent however you want, or not at all.
I’m assuming you’re running into issues because you’re writing json in a yaml file which does care about indentation, and you’re only writing json in yaml to get access to comments.
In which case it circles back around to: why not use toml? Whitespace formatting doesn’t corrupt the file, and it has built in comments.
Looking back at history, it would lead to more propaganda and more support for going to war.
A population getting attacked only leads to that population wanting to an us vs them mentality and emotional knee-jerk reactions over rational responses.