Yeah interestingly, woke up this morning, said I was blocked on computer. Phone still worked. Visiting the discord page in firefox works.
Being lazy, but might try reinstalling discord sometime later.
146 karma · joined December 22, 2011
Being lazy, but might try reinstalling discord sometime later.
In its current state, ComposeDB is focused on letting Web3 developers build fully composable applications: apps that share data models and data so they can scale together and deliver user experiences across platforms that aren’t possible with siloed databases. For example, building DMs that persist across multiple apps, reputation that aggregates across platforms, and content collaboration from multiple different interfaces.
For my involvement, I’ve joined the 3Box Labs team recently. 3Box Labs is responsible for creating Composedb and Ceramic, which is the protocol that ComposeDB leverages to deliver its functionality. I’ve been lucky enough to work on both parts in my time with the company. Previously, I was in the network security and web2 space, and started looking for something which can help move us to a decentralized internet, and hopefully to a place where users own their data. Bonus points, if whatever we build is more secure, and less prone to having my data leaked constantly.
Ceramic and composedb will hopefully provide the building blocks which allow dApps to be more easily built in Web3. Would love to know if you find the project interesting, what things you might want to build, or issues you have using the project.
We may be spending more, but it's on the order of 3-5% more (not counting debt spending), with the remainder of the income gain being wiped out by inflation.
I will say the exercise analogy is actually very correct though. Income gain helps very little at all with wealth since it helps very little at all due to inflation.
The impact of that patch would have likely caused actix to no longer be at the top of the techempower benchmarks.
That's actually my main sticking point on this being mostly on the maintainer. From the actix documentation, releases, and promotion, I never got the feeling that it was _not_ meant for production. Even to the point of the comment "Microsoft uses this in production".
And suddenly, "It's creative/fast/research/whatever"? That really feels like trying to sidestep findings because you don't want to lose your spot in the techempower benchmarks. Even more so, when the documentation, etc. is not updated to reflect this new focus, and there's no announcements about it.
I think most people kept hoping they weren't at that point, and could actually move forward without forking.
Hopefully gotham or rocket gets around to updating.
Sure they are. There's a number of projects out there with a massive caveat on the front page that says "Not for production use". They are then more than free to close issues with comments like "Hey I'm researching a new refcell implementation, thanks for finding this, but I'm more interested in speed than safety at this point."
Actix did not put up a disclaimer, and in a lot of cases, either closed issues/patches without comment, or with a somewhat demeaning comment. It was not just published as a fast and safe production ready web framework, it was promoted as such, so the author should expect patches in that vein.
There were multiple bad actors involved here, but it stems from a maintainer who took issue with anyone finding problems in his code.
They not only created issues, they also created patches. That is taking responsibility. They were contributing time and expertise back.
Having a project maintainer then call those patches boring or otherwise disregard them? That's childish. He showed time and time again he would respond without civility when an issue was demonstrated in his code.
Sadly, that led to some comments by people frustrated with the project, since they had likely invested considerable time at least using, if not more. But this was a situation that is entirely avoidable if Nikolay would have stopped promoting Actix as for production use.
Verizon NDR (formerly Protectwise) is the evolution of effective, efficient and accessible network security. Customers need no specialized hardware to rapidly deploy Network Detection and Response in any segment of the modern network — enterprise, cloud, industrial, IoT and 5G — to see all activities and record everything for comprehensive analysis, discovery and action.
Come join us if are looking to work on a very challenging problem, securing some of the largest networks in the world, dealing with a high volume of data, on a very good, agile team, with a great group of peers. We work in an amazing office in downtown Denver, near Union Station, making the commute fairly easy. We have a large selection of great lunch and happy hour options, plus the standard amenities like a kegerator and lots of food.
- Network Capture (Rust) - Develop the next generation of network capture and perform analysis of packets and network protocols. Knowledge of C/C++ and network protocols (IT and OT) is helpful.
- Platform - Processing (C/C++/Scala) - Work on the system responsible for ingesting and processing the captured network data. Knowledge of Kafka, Solr, and Cassandra is helpful. Knowledge of network protocols (IT and OT) is helpful.
- Platform - Storage (Scala) -> Work on the system responsible for storing and querying the captured network data. Knowledge of Kafka, Solr, and Cassandra is helpful.
- Infrastructure (Terraform/AWS) -> Help to enable the infrastructure powering the platform. Knowledge of Ansible, Cassandra, Solr, Kafka, and the JVM helpful.
If you are interested or want more information, please email us at ndr.careers@verizon.com. In your communication, please mention hacker news.
But the results have been dramatic. The company once had
200,000 servers and roughly 60 data centers. Now, it's
pared that down to 70,000 servers, of which 8,000 are
handling the bulk of the load. And they've more than
halved their data centers down to 23.
I'm going with clickbait title. Nothing to see here other than someone getting a temporary savings which we will see as a write off in 5 years.
Verizon NDR (formerly Protectwise) is the evolution of effective, efficient and accessible network security. Customers need no specialized hardware to rapidly deploy Network Detection and Response in any segment of the modern network — enterprise, cloud, industrial, IoT and 5G — to see all activities and record everything for comprehensive analysis, discovery and action.
Come join us if are looking to work on a very challenging problem, securing some of the largest networks in the world, dealing with a high volume of data, on a very good, agile team, with a great group of peers. We work in an amazing office in downtown Denver, near Union Station, making the commute fairly easy. We have a large selection of great lunch and happy hour options, plus the standard amenities like a kegerator and lots of food.
- Network Capture (Rust) - Develop the next generation of network capture and perform analysis of packets and network protocols. Knowledge of C/C++ and network protocols (IT and OT) is helpful.
- Platform - Processing (C/C++/Scala) - Work on the system responsible for ingesting and processing the captured network data. Knowledge of Kafka, Solr, and Cassandra is helpful. Knowledge of network protocols (IT and OT) is helpful.
- Platform - Storage (Scala) -> Work on the system responsible for storing and querying the captured network data. Knowledge of Kafka, Solr, and Cassandra is helpful.
- Infrastructure (Terraform/AWS) -> Help to enable the infrastructure powering the platform. Knowledge of Ansible, Cassandra, Solr, Kafka, and the JVM helpful.
If you are interested or want more information, please email us at ndr.careers@verizon.com. In your communication, please mention hacker news.
Verizon NDR (formerly Protectwise) is the evolution of effective, efficient and accessible network security. Customers need no specialized hardware to rapidly deploy Network Detection and Response in any segment of the modern network — enterprise, cloud, industrial, IoT and 5G — to see all activities and record everything for comprehensive analysis, discovery and action.
Come join us if are looking to work on a very challenging problem, securing some of the largest networks in the world, dealing with a high volume of data, on a very good, agile team, with a great group of peers.
- Packet Processing (Rust) - Develop the next generation of network capture and perform analysis of packets and network protocols. Knowledge of C/C++ and network protocols (IT and OT) is helpful.
- Platform (Scala) -> Work on the system responsible for ingesting, processing, and storing the captured network data. Knowledge of Kafka, Solr, and Cassandra is helpful. Knowledge of C/C++ and network protocols (IT and OT) is helpful.
- Infrastructure (Terraform/AWS) -> Help to enable the infrastructure powering the platform. Knowledge of Chef, Ansible, Cassandra, Solr, Kafka, and the JVM helpful.
If you are interested or want more information, please contact Eric Stevens ( eric.stevens1@verizon.com ). In your communication, please mention hacker news.
I'd like to think without having that, I'd take the time to put it in a day book.
In interviews, I've typically tried to draw/write out the problem (especially in terms of requirements) to help work through what I'm thinking.
That's not to say there's not a lot of bullshit around the terms programmer, developer, engineer, and architect, but there are different skill sets when it comes to programming vs engineering.
It is not however impossible to find jobs in Rust at the moment. I think January's Who is Hiring post had 5 rust job listings. Rust is still not used in a wide range of industries, but you can find a number of opportunities in crypto, fintech, security, and even a few big data shops.
And yes, there's even more jobs that aren't always out there on public channels. Good reason to attend your local rust meetup.
This article is arguing that for safety/security, you shouldn't use it. For the majority of projects that are more complex than Hello World, you'll be venturing out of "relatively safe".
One other thing that wasn't really apparent but would have made my life easier is a way to use an actor to handle a request, so I could have access to a context for thread related activities (e.g. tokio handles). It feels wrong to just use Arbiter::handle there, especially for testable code.
The actix library is fairly nice though, but still a few cases where the use of globals and/or statics introduces problems.
Definitely would not go back to just sitting.
And the SEC is responsible for improving company/shareholder relationships, so this falls under their directorate.
If they plan on having equity included, that will complicate things, since you may have variation in vesting schedules.
Total pay includes equity grants, which will increase if the company does well, thus will correlate with stock performance.
The total pay can also be manipulated by CEO's targeting short term stock gains over long term growth, which is why more companies are looking at longer vests or clawbacks for equity compensation.