Semi random fact, but there's actually a Vaporwave artist that used a number of Japanese Maxell advertisements in a distorted/looped manner for the better part of a whole album....
"... If AI-generated code cannot be copyrighted (as the courts suggest) ".
So, Supreme Court has said that. AI-produced code can not be copyrighted. (Am I right?). Then who's to blame if AI produces code large portions of which already exist coded and copyrigted by humans (or corporations).
I assume it goes something like this:
A) If you distribute code produced by AI, YOU cannot claim copyright to it.
B) If you distribute code produced by AI, YOU CAN be held liable for
distributing it.
When Nena was singing about 99 balloons we thought it was hyperbole. Few understood she was a traveler from a future where soldiers where literally shooting down birthday balloons before progressing to drones. Scary to think about the next level of escalation.
Also, Ubuntu using a non-GPL licensed userland means they can pull all kinds of tricks to allow more TiVoization in the Linux ecosystem.
Combine this with what Amutable (systemd guys) are building, and you can have monolithic, closed source, non-user-modifiable Linux distributions or flavors.
Ubuntu and companies which embed Linux into their products will love this from a business perspective.
Consider: An end to end signature-enabled, verified, attestable, Linux environment with completely closed source util-linux and userland packages, down to the "ls" and "cd". Deliciously apocalyptic.
We're two stops away from this, and there are no shortage of momentum or funding to enable teh future.
There are already very good sub-$100 lidars, especially for 2D since they were made en masse for vacuum cleaners. E.g. the LD19 or STL-19P as they're calling it now for some reason. You need to pair them with serious compute to run AMCL with them, plus actuation (though ST3215s are cheap and easy to integrate now too) and control for that actuation which also wants its own compute, plus a battery, etc. the costs quickly add up. Robotics is expensive regardless of how cheap components get.
There's a lot of skepticism in the security world about whether AI agents can "think outside the box" enough to replicate or augment senior-level security engineers.
I don't yet have access to Claude Code Security, but I think that line of reasoning misses the point. Maybe even the real benefit.
Just like architectural thinking is still important when developing software with AI, creative security assessments will probably always be a key component of security evaluation.
But you don't need highly paid security engineers to tell you that you forgot to sanitize input, or you're using a vulnerable component, or to identify any of the myriad issues we currently use "dumb" scanners for.
My hope is that tools like this can help automate away the "busywork" of security. We'll see how well it really works.
> if some women absolutely can't find something in their size from a specific brand, that makes the brand even more exclusive, like it being "for fit people only"
The elephants in the room from the raw data is it is very clear some brands do not want average middle aged women wearing their products. Anthropology seems to be the most clear about this in that they have a literal gap between their standard and plus-sized ranges that excludes the adult median woman.
Now some brands might do that out of snobishness, but I expect there is a feedback loop here:
1) Young, attractive women want to make fashion choices that signal they are young, attractive women.
2) They buy from fashion lines that don't fit average adult women.
3) Average adult women detect that the fashionable choice is these brands and feel left out, because a fair number of them would also like to be young and attractive again. And a small but significant fraction feel really left out if some clothing brand calls them a size 20 waist / fat / shaped like a rectangle. Clothing brands detect this in their customer studies and respond appropriately.
4) People who just want clothes buy from H&M or wherever and don't write articles about how hard it is to fit clothes.
"Women" isn't really a homogeneous category when it comes to clothing, there is ongoing fierce competition between lots of different sub-groups of the female population to signal lots of different things. Men have it a bit easier because there is basically a 4-quadrant choice between upper & lower class, formal & casual with a lot of intricacy for people who care a lot about what brand of black leather shoe they own. Young girls are closer to men in that they aren't really trying to signal anything at that age, so clothing fits are a lot easier to manage.
Provenance is a DAG, so you get a partial order for free by topological sort. That can be extended to a compatible total order. Then provenance for a node is just its ordering. This kind of mapping from objects to the first N consecutive naturals is also a minimal perfect hash function, which have n log n overhead. We can't navigate the tree to track ancestry, but equality implies identical ancestry.
Alternatively, we could track the whole history in somewhat more bits with a succinct encoding, 2N if it's a binary tree.
In practice, deterministic IDs usually accept a 2^-N collision risk to get log n.
The thing is, the Toyota methods relies on people on every level to work to improve processes. If you're an employee and know you'll be there 10 years down the line or even until you retire, you have an incentive to improve said processes.
Now check most Western companies: since the 70 / 80, everything is about reducing headcount. Lay-offs, outsourcing, offshoring, now the concept of spending your whole working life at the same company feels like a fever dream. So why would an employee try to improve things for the company when they know there is no future for them there? Better improve their own career and future prospect. So yeah, things like Kaizen are doomed to fail until things change.
Management Science? Only management science I read so far (with actual measured outputs and ideas) was Peopleware. Everything else was more like philosophy. Has anyone ever measured, long term results from multiple management methods? What I saw when I looked into it was simple - the Toyota Way was the model for a lot of successful companies, including Pixar.
How can the average 7zip user know which one it is?
Search results can be gamed by SEO, there were also cases of malware developers buying ads so links to the malware download show up above legitimate ones. Wikipedia works only for projects prominent enough to have a Wikipedia page.
What are the other mechanisms for finding out the official website of a software?
The headline may make it seem like AI just discovered some new result in physics all on its own, but reading the post, humans started off trying to solve some problem, it got complex, GPT simplified it and found a solution with the simpler representation. It took 12 hours for GPT pro to do this. In my experience LLM’s can make new things when they are some linear combination of existing things but I haven’t been to get them to do something totally out of distribution yet from first principles.
I've found mostly the opposite. Some well arranged windows are quite a nice anchor, I'm working on what's there in front of me. It's like bowling with bumpers in place, instead of the ball going in the gutter, the structure keeps it in the lane. I've found it necessary to devote time to cleaning and clearing windows, and sometimes I forget what's going on, and as I'm closing out the windows because I forgot what was going on, oh! there's this half finished thing that I actually really want finished.
What am I working on, what's in progress? The work space is the map. The terrain is changing as the task progresses, and so must the map, but the map is useful, even if it takes a bit of redrawing here and there.
The desktops (multiple, 3-7) are the map of the work. Part of the work is keeping the map accurate, not wadding it up and throwing it in the trash.
I suppose different things work for different people, but I started with the suggestion here and came around to skillful use of space as the work map itself.
Cleaning and updating are continuous, not a 'big bang' clear-the-desks event, mostly. But if it's not continuous, the big bang is probably better.
Some spots are problem spots, like digital notebooks, desktop icons. When I notice a problem spot, I create a recurring task to remove one X per week, or in some of the worst cases, one X per day. I have a rule of clearing out the oldest two days of email each day. I miss some days if I'm busy, but on average rate out = rate in, because I will always catch up within a day or two applying the rule that the oldest two days of email need eviction (make a task out of it, archive it, whatever) every day. Rate out = rate in
My favorite genre of graphic design is when you take a logo and work backwards to show the "very deeply thought about" construction, completely made up after the fact. The golden ratio is useful in that with a bit of fiddling you can fit pretty much anything to it. This is like catnip for "spiritual" types.
I'm biased, as I lead the Zulip project. But I think this is a reasonable place for me to post some thoughts.
Given current events in the USA, I can't emphasize enough how worried one should be about the fact that a few companies like Discord, Google (Gmail), and Meta have databases with access to the private conversations of hundreds of millions of people with their closest friends and family members, linked up with their identity.
Some of the big strengths of running a self-hosted Zulip server for your community are:
- Zulip servers are operationally simple, highly stable and easy to upgrade.
- Zulip is much better than Discord or Slack for managing the firehose of busy communities. Or at least, a lot of people tell us that they prefer the user experience to everything else they've tried, after a few weeks of getting used to it. :)
- Your community leaders get to make the policy decisions about data protection, identity, etc.
- It's 100% FOSS software, with an extremely readable and maintainable codebase that ~1500 people have successfully contributed code to. I don't think you'll find modern alternatives with a comparable featureset to Discord that are more resilient to the sponsoring company being acquired or going out of business.
- We are a values-focused organization (https://zulip.com/values/) where providing a public service is important to us all.
- Each server is completely self-contained and independent, with the only centralized services needed from us being desktop/mobile app publication and mobile push notifications delivery (which is free for community use and soon to be E2EE).
This is motivated pessimism. We knew in the 50s that breaking the speed of light was highly unlikely. We dreamed of the stars anyway. Now we refuse to dream, or to even attempt to solve the problems (a common pattern when discussing spaceflight is people who are blatantly searching for problems, rather than solutions), because we are pessimistic, devoid of imagination, and seek to legitimise our collective depression through scientific and engineering arguments.
Differing philosophies of how to interpret titles. Prescriptive vs Descriptive language.[0]
There can be different usages of the word "Unix":
#1: Unix is a UNIX(tm) System V descendent. More emphasis that the kernel needs to be UNIX. In this strict definition, you get the common reminder that "Linux is not a Unix!"
#2: "Unix" as a loose generic term for a family of o/s that looks/feels like Unix. This perspective includes using an o/s that has userland Unix utilities like cat/grep/awk. Sometimes deliberately styled as asterisk "*nix" or a suffix-qualifier "Unix-like" but often just written as a naked "Unix".
A Prescriptivist says the author's title is "incorrect". On the other hand, a Descriptivist looks at the whole content of the article -- notices the text has a lot of Linux specific info such as fcntl(,F_GETLEASE/F_SETLEASE), and every hyperlink to a man page url points to https://linux.die.net/man/ , etc -- and thus determines that the author is using "Unix"(#2) in the looser way that can include some Linux idiosyncrasies.
"Unix" instead of "*nix" as a generic term for Linux is not uncommon. Another example article where the authors use the so-called incorrect "Unix" in the title even though it's mostly discussing Linux CUPS instead of Solaris : https://www.evilsocket.net/2024/09/26/Attacking-UNIX-systems...
LiteBox is a sandboxing library OS that drastically cuts down the interface to the host, thereby reducing attack surface. It focuses on easy interop of various "North" shims and "South" platforms. LiteBox is designed for usage in both kernel and non-kernel scenarios.
LiteBox exposes a Rust-y nix/rustix-inspired "North" interface when it is provided a Platform interface at its "South". These interfaces allow for a wide variety of use-cases, easily allowing for connection between any of the North--South pairs.
Example use cases include:
- Running unmodified Linux programs on Windows
- Sandboxing Linux applications on Linux
- Run programs on top of SEV SNP
- Running OP-TEE programs on Linux
- Running on LVBS
Hobbyist game dev here. Getting into audio and music effects has been fun but I constantly feel overwhelmed. I chose Ardour as my DAW (digital audio workstation) and have been excitedly working on learning. I also bought the book “ Writing Interactive Music for Video Games: A Composer's Guide” which has been very helpful at understanding high level vocabulary.
It’s a lot of work. I slightly enjoy it but boooooy is getting into audio and music pretty challenging. It’ll be good if I ever need to know what I’m talking about when working with others… in the future where I can dedicate myself full time to game dev… One day one day…
I don’t really have a point here. If anyone has any resources, tips, or recommendations on this subject let me know.
Wirth was complaining about the bloated text editors of the time which used unfathomable amounts of memory - 4 MB.
Today the same argument is rehashed - it's outrageous that VS Code uses 1 GB of RAM, when Sublime Text works perfectly in a tiny 128 MB.
But notice that the tiny/optimized/good-behaviour of today, 128 MB, is 30 times larger than the outrageous decadent amount from Wirth's time.
If you told Wirth "hold my bear", my text-editor needs 128 MB he would just not comprehend such a concept, it would seem like you have no idea what numbers mean in programming.
I can't wait for the day when programmers 20 years from now will talk about the amazingly optimized editors of today - VS Code, which lived in a tiny 1 GB of RAM.
Love mise, didn't know about hk. Will check this out but don't think $WORK (or me) needs more than lefthook at the moment, which we're quite happy with. Wonder if there are comparisons/example projects that showcases the unique value propositions.
BTW. Pre-commit hooks are the wrong way to go about this stuff.
I'm advocating for JJ to build a proper daemon that runs "checks" per change in the background. So you don't run pre-commit checks when committing. They just happen in the background, and when by the time you get to sharing your changes, you get all the things verified for you for each change/commit, effortlessly without you wasting time or needing to do anything special.
I have something a bit like that implemented in SelfCI (a minimalistic local-first Unix-philosophy-abiding CI) https://app.radicle.xyz/nodes/radicle.dpc.pw/rad%3Az2tDzYbAX... and it replaced my use of pre-commit hooks entirely. And users already told me that it does feel like commit hooks done right.
I have also been working on an alternative written in Rust, but in my version the hooks are WASI programs. They run on a virtual filesystem backed by the Git repo. That means a) there are no security issues (they have no network access, and no file access outside the repo), b) you can run them in parallel, c) you can choose whether to apply fixes or not without needing explicit support from the plugin, and most importantly d) they work reliably.
I'm sure this is more reliably than pre-commit, but you still have hooks building Python wheels and whatnot, which fails annoyingly often.
