"""smol (likely discontinued, since author left rust)""" doesn't seem well supported and smol is used by async-rs these days iirc.
1,669 karma · joined January 7, 2016
"""smol (likely discontinued, since author left rust)""" doesn't seem well supported and smol is used by async-rs these days iirc.
"""We are going to say we used four hours of labor. This includes drive time to the primary data center. Since it is far away (18-20 minute drive), we actually did not go there for several quarters. So over 32 months, we had budgeted $640 for remote hands. We effectively either paid $160/ hr or paid less than that even rounding up to four hours. """
Software and systems configuration wise you aren't really going to be doing much different timewise then you would by doing loop de loops with AWS configuration stuff anyway. Tftp etc is just not that tough.
The flatpak solution wraps the entire Steam client, whereas Valve's approach is to wrap individual games first. Both approaches rely on the same technologies and we are looking into improving compatibility in the future."""
I'm super pleased about the sandboxing getting worked on and polished.
Flatpak Steam is working pretty great for me but I'll be happy to deal with a little weirdness as they work this out.
More worked examples with perhaps some of the recipe metaphor mixed in would be better.
I can't speak to its usability as I'm waiting on a 1.0
Fwiw use-package is pretty magic and reliable these days.
It's defined in Evil (which Doom uses directly).
Seems like you just need to figure out your bug.
Someone that cannot be promoted to be in charge of other people (that they are most likely bigoted against) or even be trusted to give a fair accounting of who worked hard today and who didn't?
How would it be responsible whatsoever to hire that person to work alongside, much less promote, the diverse cultures that the United States is composed of?
Midi 2.0 seems like its about a sweet spot that will solve real problems.
I'm looking at the midnam files that come with Ardour...
It seems like these are focused on just named patches? I see the spec can do more like parameter names but it doesn't seem like that's been the focus? Is there a bigger pile of work somewhere?
Thanks, I might poke at this a bit and see what I can get working in Ardour.
Warp seems to have one of the better api experiences but has significant performance issues.
In the async world I think
https://github.com/stjepang/smol
is going to have a pretty big positive impact on the useability of the whole system so I wouldn't rush to go all in on either async-std or tokio just yet. Last I read it was still having some fairness issues that were next to fix though.
There is also
https://github.com/withoutboats/ringbahn
Which is very disruptive in that io-uring doesn't have a natural async interface?
Having a midi device be able to describe and name its parameters and then be able to ... let me quote soundonsound -
https://www.soundonsound.com/music-business/introducing-midi...
"""MIDI‑CI will allow DAWs to discover a lot more about external gear than they can at the moment, and might even allow editing panels to be built automatically."""
I have a lot of gear that will never speak midi 2.0 but my assumption is some clever person will make a proxy (with a big list of existing gear mappings) that would allow me to select that gear and then expose a midi 2.0 interface to the DAW or a keyboard controller that was midi 2.0
This would really be huge for me and just make life a lot better around the studio.
What are your thoughts on MPE and Midi 2.0 in Ardour?
How did you layout the partitions?
What's on the 512m internal?
I have one in the basement I've tried to install one too many times and I need to remotivate.
"Firefox has a lot of performance problems already from our architecture, we didn't necessarily integrate Sqlite in the best way on top of that"
"If you make a bad sql schema it will make it worse so maybe you should think of doing something off the cuff with json files that might be just as likely to be terrible"
It's really nice to be able to read a sql schema when you are trying to understand an application.
It would be a shame to lose that because core issues weren't addressed more broadly.
"""There are very, very few politics stories — almost nothing about the Trump/Biden race, for instance."""
They explicitly bounded what they meant by politics.
These are largely matter of architecture design and graphql doesn't really fix those problems (my sense is it will make those problems harder actually).
It seems like exactly the ORM solution/problem but even more abstract and less under control since it pushes the orm out to browser clients and the frontend devs.
ORM suffer from being at beyond arms length from the query analyzer in the database server.
https://en.wikipedia.org/wiki/Query_optimization
A query optimizer that's been tuned over decades by pretty serious people.
Bad queries, overfetching, sudden performance cliffs everywhere.
Graphql actually adds another query language on top of the normal orm problem. (Maybe the answer is that graphql is so simple by design that it has no dark corners but that seems like a matter of mathematical proof that I haven't seen alluded to).
Why is graphql not going to have exactly this problem as we see people actually start to work seriously with it?
Four or five implementations in javascript, haskell and now go. From what I could see none of them were mentioning query optimization as an aspiration.
Anything on the volume is almost by definition important.
But a single bit flip and it can be complete garbage.
It would be lovely if someone, far more clever then me, layered fountain codes
https://en.wikipedia.org/wiki/Fountain_code
at a tasteful spot.
https://www.youtube.com/results?search_query=using+blender+2...
Being able to work in 3d is like a superpower that is just laying there waiting for you :)
Sitting on irc with 100 channels full of randos,
Emacs modules that aren't irc but also process text coming through for X or Y,
misconfiguration,
mime link handling,
irc protocol handling,
sloppy bot making "hey the builtin pretty printing for python code snippet had more implications then I anticipated",
"stuff" running in emacs in between network and the irc client,
add that to "noone seems to talk about or care about security issues in Emacs",
yeah a big pile of risk that pretty tough to just write off, for me, to that point I think it's bananas.
Especially when compared to the trivial alternative of sandboxing another client that has much less surface then a fully configured single process Emacs.
You are doing what you are doing and on some level we aren't too far apart in viewing the safety of a sandboxed raw emacs+some tight set of irc+a convenient plugin X and Y vs another irc client sandboxed. But I bet you aren't doing that.
I really dislike the words "threat model" in security conversations like this.
Neither of us has actually done any of that formal process for this, so why ask for it?
I think Emacs should change enough that thats more viable then it is today.
Really you are only poking at one set of vulnerabilities anyway?
Why argue for more complacency? There is plenty of that, it never needs a champion.
I'm not aware of any serious bugbounty programs for Emacs.
Emacs exploits would be immensely valuable in the right contexts.
It's a garbage collected language with parsers that have been run a few millions times so its not new code but...
I generally don't do much network anything except across secure lan.
I personally think using Emacs for irc or chat is bananas.
Emacs can be sandboxed but mostly isn't as people do so much with it and the current model is for a single main process usually.
It could evolve though and I think its inevitable that it will.
Fwiw I think not just Emacs but all the ditors are more at risk from supplychain attacks and build scripts from the internet.
We'll see.
Unusuable between 14:20 and 14:28pst today :)
Is there a public ops page for those perf numbers?
-thanks for fixing e2e, cross signing was huge improvement
https://git-annex.branchable.com/special_remotes/ipfs/
It takes a little bit to work out why you want it and why its so much better in that unixy way many of us insist on vs git-lfs (supporting ipfs should be a clue there).
*as a warning some of the defaults in last years git-annex 7 versions were aggressively annexing files in the git archives but fixed now.
The matrix home server has horrible lag spikes at some times of the day.
The e2e implementation was pretty miserable until a few weeks ago but is now pretty smooth sailing.
Been using it for 3-4 years and quite happy.