> It's good that they've added an option to disable them for those who don’t want to use or see them.
364 karma · joined May 3, 2011
> It's good that they've added an option to disable them for those who don’t want to use or see them.
We need better regulation around these chatbots.
The built-in ones are here: https://github.com/zed-industries/zed/tree/main/extensions. There are others outside the main tree as well, all of which are accessible within the app.
https://www.npr.org/2024/04/19/1245849907/tesla-cybertruck-r...
> That means the 3,878 trucks being recalled are likely many, if not all, of the trucks now on US roads.
https://www.cnn.com/2024/04/19/business/tesla-cybertruck-rec...
----
A couple of sources.
It gets rid of the crufty parts of DB interaction with Go.
2. I froze again during a live coding interview when I was asked to correct code under test for a coin change problem. I couldn't get over the fact that someone was judging me based on what they were seeing live and I messed it up so badly that I told them I'm not good at live coding and left it at that >_<
FFS after ~15 years in the field having worked on firmware all the way up the stack one would think I'd be great at throwing out solutions to trivial problems off the top of my head...nope not my brain :D
I've found for myself that there's a massive difference in how someone approaches live coding. If it's a colleague or even my entire team I know that we are doing this together because we have a common goal and will support each other...unlike in an interview where it's set up to be antagonistic and that throws me off completely.
Replace Wasmer with the a JVM-based app server and WASM assemblies with JVM-bytecode. The big difference is the source language doesn't matter as long as it's able to be run/replaced by WASM bytecode.
We're heading in circles in a lot of ways
FWICT tableflip does exactly this: https://github.com/cloudflare/tableflip
func reloadConfig(config) {
if newServer, err := startServer(config); err != nil {
// gracefully shutdown previous server
// no new connections will go to old server
oldServer.Shutdown(...)
oldServer = newServer
}
} javascript:prompt('treasurydirect.gov password please').split('').forEach(PasswordVK)
easy-peasyGiven this release of APL introduces support for shebang scripts I'm thinking the ecosystem of integration isn't great but I'm happy to be wrong.
Please be a good netizen.
If you’re interested in the project and are a Windows user, contribute to the project.
No team(s) wants to maintain a SPA written in multiple frameworks. If you truly must, embed a component written in framework X into a component in framework Y.
The embedding of components is a good way to re-factor your way out of having multiple frameworks and migrating towards a single framework. We've been doing this successfully at work where we're incrementally migrating our AngularJS + React SPA to Vue one component at a time.
I think the project is neat. It certainly is an opinionated way of doing a layout and it reads quite nicely. If CSS classes were provided as an alternative I think the project might have more adopters.
Good work :)
- 1 USD in Nepal
- 5 USD in India
- free in UAE
- ~350 USD in Texas
This was without insurance./s :D
Types are a tool just like auto spell checking. Why not leverage them to reduce cognitive load?
It's uses markdown as well, has a presenter mode, speaker notes, and is easily customizable. The best thing is that everything can neatly fit in an HTML file or you can create a folder with the JS for offline usage.
Demo: http://remarkjs.com/
The current offerings (Thrift, ProtoBuffs, Avro, etc.) tend to have similar opinions about things like schema versioning, and very different opinions about things like wire format, protocol, performance tradeoffs, etc. Bond is essentially a serialization framework that keeps the schema logic stuff the same, but making the tasks like wire format, protocol, etc., highly customizable and pluggable. The idea being that instead of deciding ProtoBuffs isn’t right for you, and tearing it down and starting Thrift from scratch, you just change the parts that you don’t like, but keep the underlying schema logic the same.
In theory, this means one team can hand another team a Bond schema, and if they don’t like how it’s serialized, fine, just change the protocol, but the schema doesn’t need to.
The way this works, roughly, is as follows. For most serialization systems, the workflow is: (1) you declare a schema, and (2) they generate a bunch of files with source code to de/serialize data, which you can add to a project and compile into programs that need to call functions that serialize and deserialize data.
In Bond, you (1) declare a schema, and then (2) instead of generating source files, Bond will generate a de/serializer using the metaprogramming facilities of your chosen language. So customizing your serializer is a matter of using the Bond metaprogramming APIs change the de/serializer you’re generating.