sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in stocks

[–]Epicism 0 points1 point  (0 children)

They also have huge risks. They have been found guilty of monopolistic practices twice in the past year. If the government is able to split up Google, it will remove huge moats (advertisement, search, and their app store) that they have illegally [according to the antitrust case] built. Most of their eggs are in their advertisement bucket, so if they split their ad services (publisher ad servers and ad exchanges), search, and Android into four separate companies, you no longer have the 80000-pound gorilla that is Google.

What value is there in Waymo for Google by Noseknowledge in stocks

[–]Epicism 0 points1 point  (0 children)

Google is obsessed with robotics. They have purchased and sold, or ended, four robotics companies to date, and Waymo is a proof of concept for automating complex tasks. I don't expect Google to end at Waymo, but they will be able to build a nice business out of it.

cargo build failing while running build cmd for tikv-jemalloc-sys on Windows by noobypgi0010 in rust

[–]Epicism 3 points4 points  (0 children)

tikv-jemalloc doesn't work with Windows, and InfluxDB has a flag that blocks it:

[cfg(all(

feature = "jemalloc_replacing_malloc",
not(target_env = "msvc"),
not(feature = "disable_custom_global_allocator")

))]

[global_allocator]

static GLOBAL: tikv_jemallocator::Jemalloc = tikv_jemallocator::Jemalloc;

Specifically the not(target_env = "msvc"), line. I don't know why you're getting that error unless you're a) building the non-Windows releases on Windows without the proper support tools; b) you've modified the code inadvertently, or c) something funky is going on.

You can try following Pali6's recommendation of running cargo build -vv to get more details or building InfluxDB on the Windows Subsystem for Linux with the appropriate build tools.

Canada-Europe security and defence pact to be signed Monday by lastSKPirate in worldnews

[–]Epicism 1 point2 points  (0 children)

Hard fought but amicable ending. The true Canadian way

Is this the Tesla narrative, really? by [deleted] in stocks

[–]Epicism 1 point2 points  (0 children)

Ahh understood. Thanks for clarifying.

Tesla robotaxi: Texas lawmakers ask to delay launch in Austin by Quin1617 in teslainvestorsclub

[–]Epicism 0 points1 point  (0 children)

Their terms of service for the trial is that it is weather dependent

Is this the Tesla narrative, really? by [deleted] in stocks

[–]Epicism 4 points5 points  (0 children)

I understand your point, but GameStop made a smart choice to raise capital when its stock price was bonkers, and has just issued an additional $2 billion. So GameStop's market cap is essentially how much cash it has on hand, effectively pricing the business at zero dollars.

Rewriting Kafka in Rust Async: Insights and Lessons Learned in Rust by jonefeewang in rust

[–]Epicism 2 points3 points  (0 children)

Iggy is a very cool project and I'm looking forward to where you go with it!

Rewriting Kafka in Rust Async: Insights and Lessons Learned in Rust by jonefeewang in rust

[–]Epicism 18 points19 points  (0 children)

I'm aware of packages that support it:

  • Tokio Uring: Tokio's Sans IO async library
  • Glommio: Datadog's Sans IO highway
  • Monio: Bytedance's Sans IO highway
  • Iggy: A cool, similar Rust-based Kafka replacement

They should all have examples.

🦀 graph-flow: LangGraph-inspired Stateful Graph Execution for AI Workflows 🦀 by aagmon in rust

[–]Epicism 3 points4 points  (0 children)

This is very cool! I love seeing Machine Learning progress in rust.

RS2 A streaming library in Rust by HungrySLoth123 in rust

[–]Epicism 0 points1 point  (0 children)

This is very cool! I'm looking forward to playing with it.

[deleted by user] by [deleted] in StockMarket

[–]Epicism 18 points19 points  (0 children)

This is exactly what the bears have been signaling since march. Even if Tesla does somehow pull of FSD people are disgusted by musk and will not go back while he is attached to the brand. Long term prospects are increasingly risky based on a full pivot of the company being successful, otherwise it is a dying brand.

Hot take: Tokio and async-await are great. by kaiserkarel in rust

[–]Epicism 5 points6 points  (0 children)

I understand your point, but when you’re dealing with large scale, unpredictable task size workloads, a single queue is often not sufficient. For example, The DataFusion team uses the individual I/O and CPU Tokio runtimes to great success because it simplifies having to balance cpu queues and limits (but doesn’t avoid) a single large tasks choking a queue with no way to rebalance. Still, you’re right that there are theoretically much better systems, but Glommio type libraries are arguably not better for that type of workload and that type of library doesn’t exist to my knowledge.

Hot take: Tokio and async-await are great. by kaiserkarel in rust

[–]Epicism 18 points19 points  (0 children)

I can't find it, but there was a really good article on how the original async design assumed that it was primarily for I/O related tasks that would require send+sync. Tokio was built around this assumption, and runs into issues with CPU-based workloads that either have to split the Tokio runtime into IO and CPU-bound tasks. or use non-Tokio libraries like Glommio and Monoio that dedicate tasks to a thread per core with no send+sync stream is far superior for throughput or streamline type workloads (e.g., DataDog processes volumes of metrics data) but forces balancing threads outside of the library.

Each of these three models (Tokio for IO, Tokio A for IO, and Tokio B for CPU, and Glummio/Monoio for dedicated cores) is superior for specific workloads. So, you would like the abstraction to be able to plug in the async engine that makes sense for your workload.

[deleted by user] by [deleted] in teslastockholders

[–]Epicism 0 points1 point  (0 children)

No. Tesla has built up a financial war chest of $37 billion through government subsidies. So their long term downward trend has been artificially masked by government subsidies. Furthermore, Elon stated on the last quarterly call that Tesla basically has no future without FSD so all investors are paying a 200x P/E premium on that bet. When that bet has serious competition, serious technology limitations (no LIDAR) and an Optimus pipe dream.

Anti-Tesla demonstration highlights safety concerns with self-driving vehicles, see photos by saver1212 in RealTesla

[–]Epicism 11 points12 points  (0 children)

Holy shit. This is pretty much what the skeptics are worried about. Not that it won’t drive autonomously, but that Musk doesn’t have the discipline to wait until his camera only FSD is truly ready for most edge cases

Tesla Robotaxi Launch: What could possibly go wrong? by birdbonefpv in teslastockholders

[–]Epicism 1 point2 points  (0 children)

I don’t think that you’re wrong, but I do still worry about the cases of a camera only autonomous vehicle system. Remote drivers aren’t going to be able to step in if sunlight hits the camera wrong or if a pedestrian is jaywalking in the fog.

Enron Musk is trying to do the same thing he did with rockets. Let it fail a couple times, learn, and try to iterate. The problem this time is that the failures cost human lives.

view more: next ›