I had a switch wig out today and whatever it was doing poisoned all the dhcp leases on the network as they came up for renewal (assigned IPs on the wrong subnet - even though it wasn’t supposed to assign IPs at all). It took me a very long time to figure out, because not everything failed at once. Plus, even after I’d swapped the switch, some devices just started working, and others needed their leases reset manually. An hour in, my wife was in the fetal position clutching a squishmallow.
The switch (that I’m returning today, after it failed completely yesterday evening) is a bit fancier than your average switch. It kept reverting to default settings, including its default IP address - which meant it was not using the same set of networking instructions as my router, preventing everything it was connected to from accessing the internet.
I feel like so many people talk about how it’s not searchable or other concerns but for me I don’t really care so much because there’s an even bigger deal breaker which is their license agreement, where you sign away the property rights of anything you post, giving away your entire open source project… This alone should disqualify it for any work of any creative sort. They own things you give them. I would never use it for development because of this.
Is this an actual thing or is it a misinterpretation of the standard boilerplate “you grant us a non-exclusive non-transferrable license to do the basic things that make a post visible to other people on the internet” message that every platform where you post stuff has?
Discord performance is inversely proportional to the number of servers you’re in. Until Discord addresses this, it’s a shit tool for this use case unless you participate in a tiny number of servers in one facet of your life. Unlike chat tools like Slack that allow you to focus one server or community tools like forums, Lemmy, or VCSaaS which don’t consume resources when you don’t use them, Discord just tanks everything. Since you can’t easily hop in and out (something community tools let you do because, you know, you’re not constantly polling the server), you can’t self regulate.
Every single gaming community, coding community, project, store, hobby group, friend group, and professional group (study group too) has their own Discord. It’s a goddamn nightmare because Discord does not prioritize basic community functionality. Voice and streaming kick ass, but I need some server management and resource optimization.
WebCord is a beast! Maybe runs better for you.
Basically Discord desktop client experience, but privacy (well.. as much as you can have with discord) from the browser-version. (minus discord desktop client exclusive features of course)
Do you have trouble in other programs with Discord running, especially resource-intensive ones? That might have been a better way for me to phrase that.
Anectodal, but I do not. Obviously most channels I am not actively engaged on or have muted but I have over 40 servers I am part of - with no impact to other applications.
<span style="color:#323232;">SELECT * FROM drinks WHERE alccontent > 0.15 AND type = "wine" AND vintageyear < 2010 LIMIT 1;
</span><span style="color:#323232;">DROP TABLE drinks;
</span>
The SQL knowledge might be for analytical (OLAP) rather than transactional queries in which case it’d be entirely separate to the website work. Maybe the design of the site would change based on how people are currently using it, and they want someone that can look at rhe data? I’m unsure.
At the simplest, it takes in a vector of floating-point numbers, multiplies them with other similar vectors (the “weights”), sums each one, applies a RELU* the the result, and then uses those values as a vector for another layer with it’s own weights (or gives output). The magic is in the weights.
This operation is a simple matrix-by-vector product followed by pairwise RELU, if you know what that means.
Where modelWeights is [[[Float]]], and so layer has type [Float] -> [[Float]] -> [Float].
RELU: if i>0 then i else 0. It could also be another nonlinear function, but RELU is obviously fast and works about as well as anything else. There’s interesting theoretical work on certain really weird functions, though.
Less simple, it might have a set pattern of zero weights which can be ignored, allowing fast implementation with a bunch of smaller vectors, or have pairwise multiplication steps, like in the Transformer. Aaand that’s about it, all the rest is stuff that was figured out by trail and error like encoding, and the math behind how to train the weights. Now you know.
Assuming you use hex values for 32-bit weights, you could write a line with 4 no problem:
That’s cool, though honestly I haven’t fully understood, but that’s probably because I don’t know Haskell, that line looked like complete gibberish to me lol. At least I think I got the gist of things on a high level, I’m always curious to understand but never dare to dive deep (holds self from making deep learning joke). Much appriciated btw!
Yeah, maybe somebody can translate for you. I considered using something else, but it was already long and I didn’t feel like writing out multiple loops.
No worries. It’s neat how much such a comparatively simple concept can do, with enough data to work from. Circa-2010 I thought it would never work, lol.
Only 1288 lines? Can I raise you a 6000+ lines stored procedure that calls to multiple different sql functions that each implements a slightly different variation of the same logic?
Mine look similar except the body is mostly “the X was doing Y, but it should’ve been doing Z” or “the docs say bla, $link”. I try to separate the individual “update A to do B” in separate commits, but sometimes it just isn’t possible.
We squash everything (and rebase rather than merge) so I don’t worry much about the individual commits. I like that main is pretty concise and doesn’t have a ton of work-in-progess stuff in the log.
We are mortal enemies you and I 😄 I’d much rather have a descriptive commit history than huge commits which make git blame meaningless. Function over beauty for me.
A nemesis! I’m pretty lucky I guess that no one at my workplace has strong git opinions that differ
Do you have multiple people’s commits being squashed together? Or how is blame being made useless for you? I’m at a rather small company where generally it’s just one person working on a thing at a time. The blame will point to their squashed commit that, if they wrote a good message like the top of this thread, will give you a lot of context.
Imagine finding a bug in angularjs, doing a git blame and finding this commit
feat(module): new module loader
211 changed files with 1,051 additions and 1,242 deletions.
AngularJS isn’t even the worst offender. I’ve seen backports of multiple fixes getting squashed into one commit for “a clean history” with all the useful commit messages ending up in one commit.
Many user stories I’ve seen implemented in a sprint take multiple days to write. Sometimes they have 5+ commits with a multitude of files changed and (if done right) each commit has an explanation why something was done or at least what was done. Having a granular view of changes also allows finding related changes quickly with less code to read.
If someone changes the implementation of a function call in one commit and it introduces a bug, it’s nice to have only that change instead of the entire class with it and changes in other files too. Additional changes mean now you have to read through more code to be sure that the function implementation change was not done due to a modification of the class or whatever else was changed which might be the actual source of the problem.
IMO squashing commits has its uses. It’s a tool in a toolbox, but it’s not the only tool.
My squashed commit messages typically enumerate everything I changed and why.
IMO squashing commits has its uses. It’s a tool in a toolbox, but it’s not the only tool.
I think we agree on this.
One case that has come up for me several times: working on a feature, committing as I go. And then I realize some of what I did won’t work or isn’t what product actually wants. Leaving those commits in the history that show the function doing the wrong thing would be misleading. Especially if that was never actually in production or left my local machine.
I guess I have an unspoken belief that every commit on main should work, but you could achieve that with tags instead.
I was recently spelunking to try to find why something in old code was the way it was. I found the commit where they changed the line, but it was orphaned from the larger context. The message didn’t say more than like “change field from footype to bartype”, but not why. So I had to try to piece together what other changes were part of this change. If it had been a single commit that showed them like adding the new field, new model, and whatnot, it would have been clearer to me that those things all go together.
I have heard about Redox. What’s the difference between a microkernel and a kernel? Does redox use the linux kernel? Or has the guy written that in rust too?
Well, think microkernels as the bare minimum. They give you just enough to write your own OS on top of that: only the bare essentials run in kernel space, whilst everything else runs in user space and has to communicate with the kernel. Compare this to a monolithic kernel, like the Linux kernel: here, the whole operating system is run in kernel space, which means that data doesn’t need to be moved between user and kernel space: this makes the OS faster, but at the cost of modularity. Redox doesn’t use the Linux kernel, it uses its own microkernel written in Rust.
Edit: A good example would be driver. In a microkernel, these run separately from the kernel and interact with it when needed. In a monolithic kernel, these drivers would be included in the kernel itself. They both have their pros and cons: if you’re interested, feel free to look it up.
No problem! Actually, System76 is currently working on rewriting the COSMIC desktop in Rust (or really, just writing a new DE in Rust). It’s a pretty ambitious project that should hopefully get released some time this year. I wouldn’t be surprised if the lead redox dev was working on it too: low-level Rust knowledge is exactly what they need.
Always on hjkl to move, and always ready to insert (i), append (a) or insert before (O) or after (o) line and fast escape with esc.
For search and rescue missions usually use the /.
They need a vim drill before combat.
The point would be to be outside. Were traveling right now and I can’t find the link but if you search for wolphrams life hacks type of thing there’s an article he wrote about it which was a fascinating read.
Personally I have an elliptical at home with a laptop stand on it and I love it.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.