>As this new kind of writing draws readers away from traditional media, we should be prepared for whatever PR mutates into to compensate. When I think how hard PR firms work to score press hits in the traditional media, I can't imagine they'll work any less hard to feed stories to bloggers, if they can figure out how.
I used Mercurial before switching to git. The positive difference from switching was how branches worked. I don’t know the technical details but branches on git felt “lighter” to use and maintain than with Mercurial.
Don't let the beer emoji in the program's output fool you: unlike most Linux package managers,
Homebrew has undergone a professional security audit, and is used (along with Flatpak and Ostree) by Secureblue.
This seems like such a tricky problem. There was a no-ai camera posted here recently which verified the photos were genuinely taken on the device. It was pointed out someone could photograph an ai image via the camera to produce a verified image.
Maybe it needs to be similar to SSL certificates where trusted authorities can verify and revoke verification for digital assets.
I was thinking the same thing. Apple and Google can start (as tech companies) to add signatures to images. As long as private key doesn't leak we are good. And each manufacturer can have different cert issued by higher authority e.g. Google, so it can be revoked when it leaks. They could include digital camera manufacturers (sony, nicon, canon, ...) and define a standard. Signature can be a meta tag based on hash of the image.
This would limit authenticity to images taken by official software.
You can still just manipulate the official hardware to produce the image you desire, i.e. record a video that's projected onto a wall. And it'd be fairly easy to do with existing technology too.
Once I realised I rarely read my notes, I now put them in a single note and prepend it when I add something new. It’s weird but I think the value I get from notes is in the writing of them, it’s a way of thinking rather than for recall.
Agreed, I always add to the top of my note files. You can also use timestamps so you know when something was created. Nowadays I use this just like a notebook, adding new pages to the top. You can use it to write not only simple notes, but anything you want, like for example the 1st draft of a book or report you're creating. Even some coding can be done this way.
It really is in the writing and not the referencing 95% of the time. That's why I tend to hand-write my notes. If it 's something I think I should have for reference, I'll transcribe, bookmark a reference, or something.
Think of it in terms of semantics. An object has certain properties that are immediately obvious and available: color, height, width and so on.
Properties in C# are for such values that are immediately available or at least extremely cheap to retrieve or form. Seeing a property tells me that getting the value is a very small op and has no side effects.
A method on the other hand is like asking/telling the object to do something that can take a bit of time and resources to do.
So if the value you are trying to read is expensive to get and isn't immediately available then the method approach works and as a developer I'll avoid making multiple calls to it unless absolutely necessary because the method is also a possible indication that it might change state.
That’s a good argument. I had not considered properties in those terms before, and have historically been skeptical of them in many languages.
I’m partly convinced now! I still worry a bit about property authors who don’t follow the “cheap, non-side-effectful, externally cacheable” rules, though. Perhaps there are linters in property-ful languages which would help with that.
> I still worry a bit about property authors who don’t follow the “cheap, non-side-effectful, externally cacheable” rules, though. Perhaps there are linters in property-ful languages which would help with that.
Definitely a problem when a developer goes rogue and breaks this rule. I'm not sure if there are linters that helper with this. I don't think either VS, Rider, or the .NET Compiler include any analyzers that complain about this. If they do, I haven't seen the warnings before. I generally tend to enforce this during code reviews with my team.
Can any Helix users share how the muscle memory from vim is working out? I’d really like to give it a go but I’m worried I’ll pollute my memory of basic vim commands. I’m bad enough remembering cut/copy/paste keyboard shortcuts in different OS/applications.
> I’m bad enough remembering cut/copy/paste keyboard shortcuts in different OS/applications.
Change them to be the same! It's indeed a waste to have a difference for such fundamental keybinds
Same with Helix - there is a vim layout out there, no need to use a different set (unless, of course, you can use something better, but then you should also use it in vim)
Helix has been my daily driver for a few years now, and it’s extremely familiar if you’re coming from the LazyVim setup for NeoVim. I make a few mistakes here and there if I have to use tools with just basic VI binds, but you learn to juggle them both.
The config is very well documented and it would be simple to rebind things too.
I think it's safe to say they figured it out.
reply