However you did “all of law works that way” and I’ve proven that isn’t the case.
12,512 karma · joined May 13, 2015
Author of murex (https://github.com/lmorg/murex, alt DevOps $SHELL). Contributor to open source. Also works on a few proprietary projects too.
However you did “all of law works that way” and I’ve proven that isn’t the case.
It’s like saying “hopping on one leg is part of law because there isn’t any laws that specifically disallow it”. You just end up down a rabbit hole of saying “everything is law” when you and I both know that’s not true.
I’ve cited UK law that makes a strong case for arguing Synaptics communication is unlawful. And you’re now asking for examples legislation for some other unrelated thing.
These two things combined suggest to me that you don’t actually care what I post, you just want bore me into a meaningless victory. So I’ll duck out now and let you have it. Enjoy :)
Nobody trusted Trump yet he had the loyalty of all the tech giants because they needed him to make money.
And likewise, AI, and thus the global economy, are dependent on Nvidia. So there was no financial incentive for him to leave if it were just a matter of trust over his inability to keep his penis in his pants.
And let’s remember, this isn’t new news. Nvidia have been aware of this for a year already and it wasn’t a problem until recently.
So what’s changed? The obvious big thing is American government. The Democrats have made it very clear that they’re not going to tolerate any more shenanigans. So removing Haung is a great way to reduce the risk of any financial penalties for Nvidia’s deals with China et al.
In America it might not be. But the UK does have some protections against this kind of bullying. And this would fall under UK jurisdiction so UK laws apply
> All areas of economic activity have this exact same problem. Employment, debt collection, warranties, housing rentals, and many other things regularly involve pages upon pages of pointed threats written in legalese that don't have any actual laws behind them,
Again, in UK law this isn’t the case. For example the UK has significantly stronger employment laws than the US.
In short, not everywhere is governed by lax US laws, thankfully.
Of course, an American company can still threaten a Scottish citizen over bullshit patent claims if they wanted thought the individual didn’t have the finances to take the company to court. But that wouldn’t be lawful communication under Section 70B: Permitted communications of the Patents Act 1977. And thus not an example of your point about how all laws behave like that.
Which then comes right back to my original comparison of a protection racket. The one you originally objected to
A comment that the GPs you’re defending was objecting to
What I’m saying is that not all UK law works on the basis of accusations without evidence, like the GP argued.
Take this specific example, UK civil law does say the initial communication doesn’t have to include the patent numbers. However it does go on to say that if threats are then made then that information should be disclosed
https://www.gov.uk/guidance/the-patent-act-1977/section-70b-...
If Synaptic require multiple weeks of work at $25,000 a week, to establish what patents are infringed, while also threatening to charge the developer for that time as well as further legal action, then it’s safe to assume that Synaptic didnt have enough confidence from the outset that their original claim was reasonably true.
In short, they are opening themselves up to litigation in return. But since their legal budget is vastly greater than this solo dev’s legal budget would be, they can skirt the fridges of what would be reasonable permitted communications.
BI doubt many UK judges would take favourable view with how Synaptics have handled their correspondence; if this ever were to reach the courts.
in UK law, IP infringement falls under the category of civil law. While these can be settled out of court, you absolutely couldn’t take someone to court without disclosing what property has been infringed upon.
If Synaptics did want to exercise their legal right under civil law then they’d would have to disclose what properties have been infringed upon.
Likewise, a police officer cannot arrest you without telling you what law you broke.
Technically, Synaptics cannot sue without telling you what patents you violated either. But where patent laws get abused is businesses extorting others over threats of high legal costs.
“You are stealing our ideas! But we won’t tell you which ones unless you pay us”
In any other domain this would be called a protection racket.
There is no universe in which this is a reasonable response.
Just take a look at the multiple fridge freezer attacks in the EU this year.
Yes I know. I was there too. ;)
> But that does not stop people from doing 100% vibe-coded projects.
And why should it? Let people "code" however they want to "code". Just like some people will find creative ways to play the guitar while others will just play covers.
By the way, you haven't addressed the core point posed: if people like AI output then is it still "slop" (in response to comments where people describe all AI output as "slop")
This would have generated extra profit for Nvidia. So I doubt they'd care unless the US government chose to take legal action against Nvidia. And that's unlikely to happen under the current US administration.
I think the bigger risk is what happens when they retire if we are not training the next generation of professionals.
But we are talking about popular culture here. That was never an industry where quality was measured by artistic excellence. It's an industry that is entirely motivated by mass appeal. Thus something being popular IS the measure of success.
So if AI is slop, then so is 99% of the human-made content it's replacing.
Not going to comment on your workplace specifically, but I’ve found this to be an issue with other industries like real estate long before ChatGPT were a thing.
The problem is the people who pickup the phone, greet you at the shop door, or take the photos, they’re the lowest paid juniors and thus know nothing.
So in most industries, you were always lucky to get through to someone with knowledge on the first attempt.
And, playing devils advocate for a moment, does it matter if a robot or a human authored it if people like it? People loved Magic Eye pictures in the 90s and they were computer generated too.
Eg https://hn.algolia.com/?q=curl+sh
I probably commented in some of those threads too. It sucks being old :(
It's insane to me that people would argue "we don't know when to stop so lets not implement it at all" when you can literally just stop at one toggle if you wanted. It honestly feels like sometimes people look for problems where problems don't exist.
Do you make the same argument for everything?
"You shouldn't treat yourself to a takeaway because what if you want more takeaways?"
"You shouldn't buy a car because what if you want more cars?"
etc.
It's literally there in the doc
> It’s called “East Asian Width” for a reason. As the note in the Scope section begins:
Yes. I didn't claim it defines terminal cell widths. There's a reason you need a library to translate that into cell widths. What I said was you don't need to be pratt about with printing because Unicode does define widths and properly libraries pin against that (like POSIX does).
> Terminal emulators have piggy-backed onto it because it’s fairly close to what they want and definitely better than nothing,
That's a very convoluted way of agreeing with me :)
> but if they limit themselves to this definition, they do a bad job.
A large part of the problem here is you're introducing scope creep.
> To see the most extreme example, look through Google Fonts for U+FDFD <https://fonts.google.com/?preview.text=%EF%B7%BD> and see the radical differences in aspect ratio (and size!).
You're shifting goal posts again because you're no longer talking about fixed width typefaces. Terminals have to make some concessions for turning scripts (of any language) into fixed width. If that's an issue then you shouldn't be using the terminal to begin with. There are better standards for that, such as the web.
In short, nobody is going to disagree with you that Unicode is hard and full of edge cases. But the vast majority of the stuff you describe are either already solved, already have standards, or are already out of scope for terminals.
The story you mentioned wasn’t about exclusions from each and every dictionary. It was about tools that do entirely unique things.
I know HN has a long history of struggling with nuance, but surely people must understand that it’s entirely possible to have a toggle to enable/disable the autocomplete adult filter without needing to then have options for every…single…minor…variation of that filter.
So you shouldn't need knowledge of the type-face to know the size of the printed character. If other libraries are printing the characters and then extracting the width from that, then they're doing it wrong and you should look to use a different library instead.
The bigger problem I've run into is not different libraries making up their own width assumptions. It's been libraries built against outdated versions of the Unicode standard.
> The terminal emulator must handle a lot of RtL stuff to get it acceptable. In raw mode (where dimensions are knowable) you could almost leave it to the app, but outside raw mode it’s pretty obvious that the terminal has to be BiDi-aware. But even in raw mode, you really can’t treat it as you describe, because Arabic text rendering is rather complex, full of necessary ligatures.
I think RTL is a distraction from the actual point that we're discussing. But it's worth noting that there are already CSI sequences for enabling RTL behaviour in terminal emulators. It's not something I've personally implemented in my own projects because I have no personal need for it and have had no feature requests from people asking for it who could test the implementation's soundness (unlike Chinese characters, which have seen a reasonable degree of popularity in the projects I've built). But I'm sure some other terminals support it just fine since it was added decades ago as part of ECMA 48.
To which the obvious counterargument is just “well of course they can stop at just one toggle. That’s not an excuse to have zero toggles”.
I’ve not found that to be the case. Usually the issue is more around different libraries being out of date (ie pinned to an earlier version of Unicode)
> and once you get to things like Indic scripts and Right-to-Left there are no good answers, and no cell-based terminal produces even vaguely acceptable results.
That’s because right-to-left isn’t supported and in my opinion shouldn’t be supported my the terminal emulator itself.
Right-to-left support would be handled by the client application, not the terminal emulator. The terminal is just there to offer a grid of Unicode cells. It’s not a writing composition suite.
Just like how the terminal emulator isn’t readline, it isn’t emacs, it isn’t hexdump, and it isn’t vim.
> As for meanings of string width, I’d count at least four: Unicode code units, Unicode scalar values, Unicode extended grapheme clusters, and terminal cells.
I’d already touched on the fact that Unicode widths can vary depending on what you’re measuring. But your Unicode library would/should handle most of the pain there.
When writing software for a terminal, you’re really only interested in the characters you need to loop through, their cell width, and, in some languages, the number of bytes.
As I’ve said previously, I’ve written terminal emulators targeting a variety of different renderers like SDL (so not just js+canvas), as well as complex terminal software like $SHELLs. From what I’ve built over the decades, honestly Unicode support isnt as big problem as it used to be. Sure, there’s plenty of footguns that you need to be aware of, but that’s just the nature of working with technology originally designed in the 60s/70s. Like how you need to be aware of cell widths if you intend to do any manual text alignment in client software. But at least there are libraries to make that task easier.
And if you don’t case about text alignment, then the terminal emulator will handle that for you.
I know these are all typos because she’s a really close friend and easily the last person who would be offensive to other people.
So yes, you’d be surprised at what people can typo on a phone.
- [ ] Disable autocomplete swear filter.
But finely grained options are not Apple’s way.