skysight-inc/HackerNews huggingface dataset:
No. I'm not.

https://www.washingtonpost.com/archive/politics/1981/01/14/c...
Elon Musk, Gov. Newsom Announce Tesla Moving Global Engineering HQ to Palo Alto
Sounds awful, and yet 30% of Amish girls don't want to kill themselves. So we can go off on the Amish, provided when we finish we admit we do an even worse job of protecting our daughters' wellbeing. And the Amish are a politically and culturally irrelevant minority, who exist in the general consciousness primarily as a punch line, which makes me wonder if we couldn't come up with a more constructive way of avoiding the issue.

STRONG agree on the beards.
> This example of yours would begin with an exploit (or feature) of the third-party software, which in turn managed to pivot into an exploitable hole in the kernel/base system in order to gain these escalated privileges. Securing the kernel/base system is where their focus is.

Sure, but the 'base' system doesn't really have anything that people use or that is going to have bugs. It's kind of a copout.

> just the notion that the OpenBSD team's efforts are "terrible" and "simply not sufficient".

Terrible is maybe a bit strong, but they certainly are not sufficient. There are numerous exploits and exploitation paths that pledge and unveil won't prevent, but MAC/RBAC or other DAC alternatives will.
The sentence you quote is the beginning of a paragraph that ends with “There is random noise, but the visual layer evolves the final image from the noise based upon the latent ’meaning’ in the prompt”… which is in complete agreement with what you’re saying? It certainly isn’t saying diffusion models don’t use random noise. It has the phrase “there is random noise”, that is just wholly incompatible with that claim.

Perhaps that first sentence could be more precise, but by the end of the paragraph the author’s meaning is clear: the court has a misunderstanding about the “randomly generated noise” when it believes there is randomly generated noise in both the pixel and the latent - this is not the case, there is no randomness in the latent, that exact handcrafted prompt picks out a precise spot in the model’s giant table of embeddings, that prompt will always pick out that spot in that model, and the random noise is only on the pixel side of things. The author believes the court has this misunderstanding because the court uses the analogy of “a patron makes a suggestion to an artist”, which is a scenario that DOES have random noise involved in producing the latent (the brain is an inherently noise place; an artist’s brain likely even more so).
I would wager that most people that choose to avoid trial because they feel openly threatened by the legal system. In their minds, it becomes a life or death decision, and the system puts enormous pressure convincing people that a trial would be a game of Russian Roulette. If more people started demanding full trials, the pressure would be increased.

The beatings will continue until morale improves.
Agree with everything you said. I also did the same thing basically, undergrad CS and grad math classes.

The author basically did all of undergrad math and physics, and now apparently they're planning to self-study all the grad math. The thing with self-studying is you're taking yourself out of the system, and at some point you have to inject yourself back in. I hope the author is able to do that and doesn't miss out on undergrad college too much, because it's really enjoyable if you find the right friends and you'll look back on it fondly.
Or, maybe they want to give credit where it’s due and not plagiarize?
Not trying to fight at all, but no time for someone that has such trouble comprehending something and then blames the author instead of being able to self-reflect.

Best of luck to you in life, Champ.
The key idea is you can use physical effects such as attenuating light to implement multiplication in a way that uses much less energy than the fairly complex arrangement of digital logic necessary to implement the same operation. This is roughly the method they use in the paper:

https://en.wikipedia.org/wiki/Spatial_light_modulator

I've seen a lab bench prototype of a different implementation, there are a lot of engineering problems to solve but as the paper points out the potential payoff is big.

Edit: The other key point is that one of the expensive components in transformers is effectively a giant matrix multiplication which implies many, many individual multiplications.
Did you know that there are other countries besides Brazil in the region conventionally referred to as Latin America?

https://www.washingtonpost.com/archive/politics/1981/01/14/c...
I tried it for a while, it didn't seem to have all the shows I wanted and the UX was worse than quite a few of the anime piracy sites.

Of course, anime is a bit of an oddball when it comes to piracy sites, the lack of legal enforcement combined with (from what I've noticed) that a disproportionate part of the audience are developers means there are some really good sites out there.
Do you really have to call out the entire JavaScript ecosystem like that? :)
The oft cited refrain is that colleges/universities serve several purposes aside from education:

1.) Verification, standardization, and authentication of work being done and of knowledge being gained.

2.) Networking opportunities and social/professional development and maturation in a a limited-stakes playground surrounded by others in the same social and economic class, and

3.) A sort of IQ test laundering service.
this exists basically at very large scales with companies like nielseniq and to some degree Catalina marketing. If there was a way to make money off it, they could easily produce a lot of useful aggregate item pricing dbs by region over time.
Fibers would be stackful coroutines (every coroutine gets its own stack memory, and local variables inside a coroutine are placed onto that stack). Whereas C++ coroutines are stackless - local data in those gets placed into a magic object that is created somewhere by the compiler.

Stackful vs stackless comes with a few pro's and con's - e.g. it's often argued that stackless requires less memory. However stackful coroutines can allow for preemption at arbitrary points instead of just at yield points.
When the Movies Pictured A.I., They Imagined the Wrong Disaster
What not use an old Twitter building? Seems like Tesla could get a good deal from the landlord.
It obviously is a circumstance that is occurring every second of the day. Not some hypothetical 'might be'. The parent has a point.
I moved a Gsuite client to Zoho because once or twice a week, an email from one person at the custom domain to another person in the same custom domain (company) would have their direct email get put into spam in Gmail.

You would really think that Google would whitelist emails within the same custom domain which is paying for Gsuite service. Maybe that has changed, but it was definitely a problem 5 years ago.

And we're not talking about an email which had some copy/paste of spam, we're talking about a one or two line sentence giving an instruction or asking a question to a colleague.
Been a long time since I've seen a CHIP
Against predictive optimization
Ciena announces 1.6Tb/s wavelength capacity
Imagine selecting diabetes patients at random, and asking them one by one:

"You are currently already by necessity accepting the monitoring of blood glucose invasively with device X, here is a less invasive device Y that sits under your lip, or perhaps has a fiberoptic cable running up to your lip. Would you switch to this lip-oriented device today? Or would you rather profusely refuse to use this device Y until some more distant unspecified future date where the technology Z finally robustly works through thicker layers of skin while continuing to use the more invasive device X?"

I don't claim but tend to believe they would take improvement Y over X while waiting for Z.

You actually claim they wouldn't.

I say let the patients speak for themselves.

Perhaps your claim is correct and no suitably large niche of patients would switch to the lip-oriented device.

Perhaps you are wrong and you have confirmed my suspicion of the miscommunication between patients and engineers.

Your rebuttal does not prove compliance of a less invasive lip oriented device would be lower than current invasive devices.
It's strange seeing the word "proprietary" used as if it's a positive thing for consumers.
That's fascinating. Thanks for the context.
"Railway Oriented Programming"[1] is a (functional) technique to achieve purity despite steps that could result in error states. The error states are hidden/pushed to the very edges/end of your code. So you can focus on the "happy state" for the main business logic:

> Many examples in functional programming assume that you are always on the “happy path”. But to create a robust real world application you must deal with validation, logging, network and service errors, and other annoyances.

> So, how do you handle all this in a clean functional way?

> This talk will provide a brief introduction to this topic, using a fun and easy-to-understand railway analogy.

Functional programming keywords/shorthands: option/either/monads

[1]: https://fsharpforfunandprofit.com/rop/
I was with a medical equipment manufacturer for a couple of months. The codebase doesn’t have any consistent styles, and has tons of warnings and linter suggestions lol, no tests no and barely any documentation, it was a pain in da a* to work on that codebase… all the frameworks and packages used were pretty old and out of dated (this one though is understandable considering all the approvals required form FDA and stuff)
Docker builds are not slow if you do them properly

1. Add layers properly, so that, the most changing code appears towards bottom.

2. Use a builder pattern where you build in one image and then copy the output binary into the second image (https://ashishb.net/tech/docker-101-a-basic-web-server-displ...)

3. Use Docker layer caching on GitHub Actions or your favorite CI(https://evilmartians.com/chronicles/build-images-on-github-a...)

IMHO, hadolint is a good docker linter but there is no tool in the market that helps people optimize docker images.
I was CTO from 2005 incorporation of Mozilla Corporation. You must be thinking of CEO.

FYI, I'd already run all of engineering from 2013 January on until CEO appointment, as SVP Eng + CTO.
Does this happen even if you move your client to Google Workspace/Office 365? Using one of those two should eliminate the problem. Was that your experience?
Looks stunning, but no thanks. I want analog dials and physical buttons and knobs for features like gauges, air conditioning, and volume.
If you never see something a second time, maybe you didn't need to learn it.
Imagine graduating top of the class and grinding leetcode for months to share a desk
> And from there you’ll have to convince Google that you’ve done nothing wrong.

Imagine the conversation with their support when you ask why bob@domainx.com's email was put in spam folder of jan@domainx.com's email, as both are hosted by Gsuite and presumably entirely within the Google network.

The answer, after two levels of support, was, "We don't understand why, but we can open a ticket with the developers." In the business world, you don't have time to wait for that, especially when non-technical business users are making mistakes or losing business because they can't function properly.
Perhaps, but I don't make a habit of reading blogs about jobs I don't currently have from smaller companies. Not that I have anything against them, but you still have a discoverability problem.
A few yeas back several of them moved to netflix, and a few moved to airbnb and uber. I'm sure google still pays executives well above any other company, the people I knew at the time were fairly inexperienced and new to the field, and from what I heard google seemed to undervalue them relative to what other Bay Area companies were offering at the time.

Of course, this was a few years back, I'm not sure if the landscape has changed now for better or for worse.
That's extremely true, but for writing non-fiction.

For writing fiction, it's perfectly possible to have a tradeoff writing to be evocative vs being clear and precise. Tolkien and Fleming spring to mind.
Integrating: usually none because I've never worked with an API that didn't involve building a ton of BL around their use to fit our business use cases

Building: the biggest pain is usually the language we are working in. the spec/protocol/etc don't matter, if they're popular they'll be supported in most languages. however, some languages just make building APIs hard-mode and annoying AF. even though I'm not the biggest fan of nodeJS anymore, building JSON apis with typecsript was a breeze compared to any other language. Have built both public REST and GraphQL apis.
The first three aren’t valid. As far as I can tell, RFC 3696 accidentally invented unquoted escaping there, which is not permitted by RFC 822, 2822 or 5322.

The errata are a doozy <https://www.rfc-editor.org/errata/rfc3696>, with a bad correction verified, a bad correction of that correction verified, and a reversion of the two incorrect corrections with incomplete justification (not quite mentioning the root cause, that you can’t actually use backslash-escaping outside a quoted-string like the RFC deliberately did) “held for document update” (which I suspect means that the reviewer finally realised the actual error, and decided it was too large to deal with with this way, but there are no verifier notes and I don’t know where the errata discussion records are, if they’re even public).

I wrote more, but it becomes all messy and confusing and I think I just discovered that according to RFC 2822’s and RFC 5322’s grammars, a space inside a quoted-string would actually need escaping, which would ruin "Fredd Bloggs"@example.com, which is widely understood to be valid. (This is because qtext lacks %d32 (space), which I think is accidental but it’s not entirely clear—it’s all bound up in the painful question of whether space is printable or not; see also <https://www.rfc-editor.org/errata/eid4692>. But their intent was clearly for space not to need escaping, as various examples all over the place use spaces unescaped in quoted-strings.)

So… I’m going to tip-toe gently away now and stop thinking about email address syntax for the rest of the day if I can help it.
The Death of the Sex Scene
I met someone in Seattle who was working on an optical Asic to mine Bitcoin. Is this in the same direction as this article?
Learn Rust with JetBrains IDEs – The IntelliJ Rust Blog
The author of this piece is a long time FreeBSD contributor[1]. Just maybe that person has relevant experience guiding their thoughts? He certainly is not "doing nothing and whinging constantly". Posix is not a religion - it's ok to look at other ideas, to listen to critiques. I mean Linux does it all the time - io_uring, all the ebpf stuff, a dozen forms of kernel bypass suggest to me that the posix interfaces aren't sufficient, or right for modern hardware, at least not in all cases.

[1] Here's his first commit: https://cgit.freebsd.org/src/commit/?id=026e67b69b612f90360a... with the most recent happening within the last year.

edit: fixed link
Your second point is important, but when you have recruiters/HR as the front line of hiring it completely breaks down because they haven't got a clue whether an applicant's skills are transferable or not. And they cop a lot of flack for this from developers but honestly I'm not sure it's possible for someone who doesn't even code for a living to learn how different technologies are and aren't compatible, skills-wise. Same reason we end up with unhelpful job descriptions. I think most developers would already be onboard with your second point but it's simply not up to them.
Yes you are correct. I am currently having a project, making Linux "as real-time as possible": locking memory with mlockall, isolating cores, preempt kernel patch, .... It is still not real-time because you have no guarantees, but you typically get a max jitter of 0.1 ms, which is good enough for my use case.

You could use Linux without a MMU (uClinux), e.g. on a Cortex-M, but is a horribly experience and no standard program works.
IMO, the 'x' changes it. 1x is 1 x the other number, x meaning multiplication.
The joke was more that the VN govt was slowing down internet during holidays and blaming it on sharks... since that is when it always got slower... except that doesn't take into account that more people needed internet during holidays.

Nice to hear the speeds have increased over time. It was pretty bad when I was living there. That said, the 4G LTE coverage was amazing... literally the entire country, even in the most remote areas. Another reason to look forward to going back some day.
I know some people think this is a silly question but the answer is, in my experience, yes. That's both in urban and exurban environments, in my experience.
I have noticed with India born Indians that they have questions they'll ask to try and figure out each others' caste. Things like where they lived and grew up in India, what they're parents did, etc.

It's completely alien for someone that's spent an overwhelming amount of time in western countries.
Exactly: farm equipment is one place where you really do not want to Buy American.
How I Got into Pixel Art
Yawn, said nobody who knows what IMF and BMF means and why it is the way it is. Just get Congress and their masters to stop writing tax law and kneecap every collections automation.

I’m sure whomever this author is lobbying for would love to spend $20B on a craptastic port to python or whatever and run it on commodity crapware for another $20B/year. Those mansions outside the beltway don’t build themselves.
macOS at least is definitely posix compliant - not just somewhat. It was a big part of what was needed for xserves to be competitive (alas being shiny and aluminium was not :) ). While xserves have died, macOS remains entirely posix compliant - complete with the horrific %n format specifier (although an environment variable is needed for it to be respected in non read only format strings iirc)
https://isopenbsdsecu.re/mitigations/pinsyscall/ for a contrasting opinion
I don't understand exactly how that would work. At some point, the generation would introduce new events and characters, new places or objects, and name them, but then when summarising, won't the names of some of them be lost, just because there's not enough space in the summary to name them all? The same goes for all sorts of detail, not necessarily named. At that point, what happens to the narrative about those forgotten characters, objects, etc?

The main idea, of continuously feeding the model a summary of its generation (and its dialog with the user of course) sounds interesting, but it's still not a memory. At some point, the continuous summarisation will have to grow big enough that it again exceeds the system's buffer (its "short term memory"). Either that, or it will drop so much detail from the summary that it will lose the plot.

So while this may result in longer generations, it doesn't look like it will really solve the problem of "long term memory", or long-distance dependency. It's a smart trick, but that's not enough.
Hadn't heard of langchain, here's a link: https://github.com/hwchase17/langchain
That's what I do. Mailcow on an isolated machine, 25/587 open on firewall port forwarding to it, the rest of the various services it offers are only accessible via my home network (https, imaps, there's probably more). Then, I am always on my home network.

I started out with a different variation of this that was the same, except instead of using my (thankfully static) home IP in my MX record, I got some cheap hetzner/lightsail/whatever, then routed the incoming 25/587 across a 2 node wg network to the real mail server. It worked fine but ultimately I decided I'd rather expose my real IP in the MX record than pay $5/mo not to.

Of course, the secret to making this work without tearing my hair out is that my outgoing mail server only delivers mail to the relay I pay to deliver my mail to the 3 or 4 corporate behemoths who have taken over a once great decentralized service. I have no interest in tending to my deliverability or making appeals to Microsoft or whoever. Also at a personal mail volume with 0 transactional mail, it's very inexpensive.
.. and earth would be better for it.
Ideally it would be smart about the skills, and recognise how skills transfer between technology. I feel like this is a solvable problem with the right technology.
What's the argument for why prompt generation deserves copyright protection that doesn't also imply that commissioning a piece of artwork deserves copyright protection?

If I go to a human and ask them to draw me an image, I will iterate and collaborate with my prompt just as much if not more than I would for an AI generated image. I'll look through multiple pictures and point out things I like and dislike. But I won't get joint copyright over the final image unless the artist gives me a contract assigning it. We recognize that collaboration with a human to describe a final image isn't something that usually falls in the narrow range of copyright.

So the argument around prompt generation seems like it has much wider implications than most copyright-expansionists are saying. I don't understand how to grant AI images copyright without granting a bunch of other stuff copyright too. And traditionally, we don't think of commissioning as a copyrightable act, even though it arguably has very similar elements of creativity that are being talked about here.

Is there a creative human input into an AI-generated image that isn't present when commissioning or working with a human artist? Because otherwise we're talking about a frankly massive expansion of copyright that should probably be approached with a lot more caution. I mean, some of these arguments I see for granting copyright are getting really close to outright saying that deciding what to draw should be treated as creative enough to warrant protection. That's a wild thing to say, that has so many implications beyond just AI images.
> POSIX won because it was first. Simple inertia keeps it there.

UNIX only started wide distribution in 1975. The first POSIX standards were not proposed until 1988. To pretend otherwise is to attempt to rewrite history. There were complaints about UNIX API's long before everyone standardised on POSIX. Not before, not during, not after, have the elephant riders really gotten down and gotten to work. And where they have, as others have pointed out, it's things like io_uring which have emanated from the Linux community itself.

Embedded API's may be better in many respects, but that does not mean that any particular vendor's implementation should be the new basis for a standard - especially if they cannot or will not support the existing deployments out there. Software developers love a clean slate, solution providers and integrators need to be able to deploy something to their customers and be able to guarantee interoperability etc. It's a pipe dream neutered by the practical reality of the real world.

Nobody is arguing that they are completely wrong - it's just that it's long been giving off a "young man shouts at cloud" kind of smell for a long time, and it's not really that useful other than to give other people who have been hurt by POSIX a place to vent before they go off for another scrum, kanban, retrospective, or long lunch and forget about it until the next article.
Stern tried this a long time ago to compete with Golden Tee Golf tournaments, since those games were paying people cash and killing pinball in street locations like bars.

The problem was stopping nefarious players from taking the glass off and rigging the score. It's an impossible thing to prevent.