Why wouldn't it? The ASF has a long history of incubating new FOSS projects. Some graduate and become household names. Others fail and end up in the attic. The ASF can provide organisational support and generally fosters good communities.
My point was this is a crowded market now, why would they pick a platform that is not known? I did search HN and this platform was only shown once 2 years ago, and from their releases, they are still 0.42 after two years.
It might sounded that I’m against the move, but I’m just curious as what apache found in the platform to get incubated
I see far more SVG injections than SQL injections these days, but YYMV. My programming ecosystem has very robusy SQL libraries, from simple prepared statement bindings to complex ORMs and everything in between.
I've seen it quite a lot in my career: even when prepared statements are available and easy to use from a SQL client library, many programmers will simply not use them, in favor of format strings and string concatenation (maybe with an attempt to quote/escape user input).
Just having support for the right way isn't enough. You have to put up roadblocks when people try to go the wrong way.
Why is a format string or string concatenation (or interpolation, what I would use) the “wrong way” when all user input (more precisely: all string literals) are properly escaped?
The main reason is that a lot of the reason comes around that it is incredibly difficult to do this in a general case just because of the grammar of SQL. Especially with the very different dialects, in the worst case you can get unintended remote code execution[1]
There's an incidental performance benefit on some database engines as well. When you write a SQL query, in general the database engine has to compile this to a form it can use
If you use raw string concatenation, "SELECT USERS FROM table WHERE id=1" might compile to something like (pseudocode below)
def prepstatement1():
...
So if you use an explicit prepared statement[1], something like "SELECT USERS FROM table WHERE id=?" might compile to something like
def prepstatement2(id: int): # <--- notice the new parameter here
...
Some database engines also have the ability to cache a prepared statement and so these are a lil bit faster. Remember, your database has to still compile the string concatenated case, it's just a little bit hidden.
Thinkpad laptops thankfully have a BIOS option to revert the behaviour to normal, where F1-F12 perform their nominal functions. I'd probably pay an extra €50 for a laptop that didn't come with a stupid Fn button at all. Might want to throw some more money at a few more keyboard modifications: my bottom row is Fn CTRL Win Alt Space AltGr PrtSc Ctrl; that PrtSc button clearly has no business being there. Arrows & PgUp/PgDown are too small. Backspace is too short. Etc.
Thinkpad laptops thankfully have the option to switch Fn and Ctrl Key in the bios, because that Fn in the bottem left is reserved by my muscle memory to ctrl and I won't change that.
They switched the Ctrl/Fn position a year or two ago so people like you would stop complaining. Of course this means that instead you have anybody who's used a thinkpad in the last 30 years complaining about the switch. It's a little better now because they made the keys the same size, so after you switch them in the BIOS you can physically switch the keycaps around.
> thinkpads have always had the Fn key on the bottom left
It’s good that after 30 years they’ve realised their error and have finally fixed it. On Windows and Linux, Ctrl is the most-used-modifier-key and bottom-left is the most-easy-to-find-key-position. Putting the most used key in the easiest-to-find position shouldn’t be a hard decision to make.
You need Fn anyway because even 16" now come without a navigation block and even if you have it (asus tm420 though they ditched that too) you have no way to make PrtScr, Break, ScrollLock.
The real atrocity is placing it on the left side when 90% of the most used combos are on the right eg Fn+arrows for paging and home/end.
It could be way better if Fn was on the place of ContextMenu - Thinkpad already used it for the stupid PrtScr and now even more stupid Copilot key.
I wouldn't buy a laptop that requires the use of Fn for any key I commonly use. I don't particularly care about PrtScr, Break or ScrollLock. Can't remember the last time I used either of those. But Home/End/PgUp/PgDown are requirements.
My new thinkpad has an interesting mode where if you accidentally hit fn in combination with a non-function key, the firmware reinterprets the key as Ctrl. Fn+C on the keyboard gets sent to your OS as Ctrl+C. It's pretty handy.
Yes, normally a BIOS setting on laptops I think. Before changing it I was hitting sleep constantly since they'd put it on F1, jammed up next to escape.
1. As others have mentioned, males were excluded from vaccination until relatively recently. This seems like such a stupid decision in hindsight. When I (male) got my vaccines, I was told that it wasn't routinely done in boys "because of availability issues", which I took to mean "because it's expensive".
2. Initial vaccines offered protection against 4 strains of HPV, newer vaccines protect against 9. People who got the older vaccines remain susceptible to the other 5 strains.
3. It can take years for an HPV infection to become dangerous or cancerous.
4. This last one is speculative, but I assume that when a woman tests positive for HPV or cervical cancer, their partner is also looked at. With the rates of symptoms and cancers going down in woman, their partners might fall through the gaps: there are no routine tests for males.
The test for males used to be putting acetic acid on the genitalia and looking for spots under a blacklight, right? So what is it now? Blood test for the DNA?
> An easy way out of this is universal basic income and universal mortgage/rent freezes now.
Of all the unlikely things to happen, these seem like the most unlikely. There's a bigger chance of a violent mob blowing up every datacentre on the planet than there is of UBI being implemented within the next century.
Yeah, the prices are actually down a few pp compared to record highs recorded before the war. The war might even exert some downward pressure. It increased the cost of living, thus reducing demand for comparative luxuries like new devices. Laptop and smartphone markets are contracting heavily right now, even for devices with stable prices enabled by long-term RAM procurement.
I was also wondering if it will result in Helium shortage and even higher prices the next few years, then/if it will be all over, new fabs might also come online and it will be the opposite - a glut. I believe that follows the historic pattern of boom and bust cycles of chip production.
That is correct - this is the whole story. Everything else you've portrayed the author as saying is misleading.
The author believes if you have a friend who cooks, see if they have a recipe. You believe there's no harm in going straight to Claude in the same scenario.
reply