innocentoldguy

Schmidt, M. S. (2018, June 14). Top Agent Said F.B.I. Would Stop Trump From Becoming President. The New York Times.

Also, whistleblowers within the FBI have come forward in recent years to:

• Accuse Timothy Thibault of running cover on Hunter Biden's laptop.

• Accuse the FBI of manipulating case files to inflate the domestic threat perception towards conservatives.

• Accuse leaders within the FBI of "weaponizing" the agency against conservatives.

• Complain about retaliation when raising concerns about these and other instances of bias and misconduct.

Isn't this common knowledge?

I don't know where you're getting this idea since one of the main goals of the Electoral College was to protect smaller states from more populous states dominating presidential elections.

Boudreaux, Paul. "The Electoral College and Its Meager Federalism." 88 Marq. L. Rev. 195 (2004). Available at Marquette Law Review.

You mean this one?

https://www.usatoday.com/story/news/factcheck/2020/09/10/fac...

The Trump-hating FBI disagrees with you.

https://www.reuters.com/world/us/exclusive-fbi-finds-scant-e...

Elixir is "more secure" than Go due to its isolated processes, functional processing, and immutable data.

The electoral college is one of the ways we protect the rights of the minority. Without it, we’d be a democracy and that wouldn’t be good.

> Most of that doesn't deserve to be called an improvement.

Hard disagree. The platform is objectively much better than it was under Jack Dorsey.

> The algorithm isn't open enough that anybody can see if what it's doing matches the code.

Fair, but more is available than before.

> ...in partnership with the Indian government as well as individual Republican politicians.

Would you prefer X break India's laws, specifically Section 69A of the IT Act? I suppose they could do that and then the Indian government would shut them down in India.

Also, are you talking about X suspending Ken Klippenstein's account for doxxing JD Vance? X's rules explicitly state that doxxing people will result in a suspension, so maybe Klippenstein should have thought of that before posting Vance's home address and most of his social security number.

Here's X's policy against what Klippenstein did, which applies to everyone: https://help.x.com/en/rules-and-policies/personal-informatio...

I'm not sure what you mean by "Nazi" and "arbitrary moderation." Can you clarify?

Nothing game-changing? How about:

• Long-form content

• Video streaming

• Grok

• Ability to edit posts

• Bookmarks

• Communities

• Better verification system

• Encrypted direct messages

• Cashtag feature

• Bold and italic text formatting

• Open-sourced algorithm

• Premium features

• Improved search

• Improved analytics for content creators

• And most importantly, less First-Amendment violations in secret partnership with the federal government

How did Musk "fuck [Twitter] up worse than ever"? It has more functionality and is more stable since Musk bought it.

It's a name that accurately describes the ultimate goal of the technology. It's not there yet, and Tesla makes it clear that this is the case. I don't see an issue with it and it works exceptionally well as is.

I'm not surprised. I have owned multiple RAM trucks, a Toyota Tundra, and a Ford F-150 in the past and I like my Cybertruck better than all of them. It is quiet, fast, powerful, drives itself, has tons of cargo space, and its turn radius is amazing. Because I have solar panels on my roof, it only costs me about $20 a month to charge it.

Yes, it is.

It's called "Full Self-Driving (Supervised) Beta" and you agree that you understand that you have to pay attention and are responsible for the safety of the car before you turn it on.

I've been using a Kobo Clara Color for several months. I love the size and functionality, but the color isn't that big a deal since I'm not reading picture books.

I used to use a Kindle Oasis, but I like Kobo's software better than Amazon's, so I switched.

My issue with Google is biased censorship and too many garbage results. I have been using Kagi lately and the ability to blacklist domains I never want to see has helped increase the value of my search results.

I think "cannot do" is a misnomer. Shouldn't it be, "consciously designed not to do"?

Server-side state management offers several advantages over in-browser state management, such as:

• Better security and privacy.

• More reliability and control.

• Better and more predictable performance since it removes the burden from the client device.

• More accurate user metrics.

• Minimizes browser compatibility issues.

• Better scalability when prioritizing user data security.

• Easier debugging.

(Edited to fix bullet formatting.)

I like the look of Elixir over Gleam for sure because:

• Elixir allows for more flexibility and faster prototyping. • Elixir's ecosystem is superior and more mature. • Elixir compiles to BEAM bytecode whereas Gleam compiles to Erlang which then compiles to BEAM bytecode. • Elixir supports Lisp-style macros. • Elixir excels at web development, data processing, and distributed systems. • Elixir's OTP implementation is better.

Since Gleam doesn't support macros, my guess is that Gleam isn't going to be able to run Phoenix-like or LiveView-like frameworks, but I haven't really looked at it, so I could be wrong (edited because what I said wasn't clear, and probably still isn't).

I don't mean to knock Gleam, but it feels to me like a project that came about to add static typing to what Elixir already does, and while it has accomplished that, it has failed, so far, to live up to all the other great things Elixir and Erlang do. I know it's still a young language, so maybe someday they'll get there, but they're not there yet. After coding for 33+ years, I just don't find static typing to be all that compelling or important to me, so I would never choose Gleam over Elixir as things currently stand.

The reasons I reach for Elixir and Phoenix over any other languages and frameworks for web development are:

1. Excellent tooling (e.g., Mix, IEx, Formatter, testing, debugging, Credo, ExDoc, Livebook, etc.)

2. Excellent concurrency and fault tolerance.

3. Ability to handle extremely large numbers of simultaneous connections in an efficient manner.

4. Lightweight processes that handle both vertical and horizontal scaling.

5. Phoenix channels.

6. Full-stack development support.

7. Supervision trees.

8. Macro support.

9. Interoperability with Erlang.

10. One of the most supportive communities I've experienced.

11. Excellent error messages and debug support.

12. Excellent testing framework.

13. Good support in my editor of choice (Helix).

14. Mike and Nicole at Pragmatic Studio (for teaching new hires who don't know Elixir).

I've had the opposite experience. I've worked at several companies that migrated from Go to Elixir because the return on investment DID justify the effort. For example, Elixir allows us to do hot code deployments, uses a tweezer approach to self-healing as opposed to Go's sledgehammer approach (when paired with K8s, otherwise Go can't self-heal at all), and Elixir's immutability makes concurrency less error prone than Go's imperative nature.

Same! I've had a lot of success training Python, Ruby, and JavaScript developers in Elixir and Phoenix. I've never had the "You can't find devs who know Elixir" problem that I occasionally see.

It looks like others have address the first 90% of your post, so I'll refrain from commenting on that. I am curious about your timer code, though, because the timer shouldn't be firing at all unless the task associated with it has completed successfully. You shouldn't run into an issue where a timer is re-queueing the same task in Elixir.

In my experience, Elixir is one of the easiest languages to pick up and get stuff done quickly. It has excellent tooling and deployments ARE 10X cheaper (if not more). I've never converted a project to Elixir and not had the associated costs decrease dramatically.

Also, I don't find typing to be an issue in Elixir due to the way the language works (pattern-matching, guard clauses, immutable data, etc.). Maybe I just have a talent for remembering types, though, because strong typing has always been a huge meh for me.

Elixir’s tooling is awesome, in my opinion.

Flame is so easy to use, as are most things in the Elixir world. I can fathom using anything else for web programming.

I don't mean to hijack a conversation about ReStructuredText, but if you're looking for a markup language that gives you more than Markdown, look at AsciiDoc rather than ReStructuredText. I have written technical documentation using all three for years and AsciiDoc is superior to both ReStructuredText and Markdown, in my opinion.

For example, Markdown's and ReStructuredText's support for tables is cumbersome to say the least. AsciiDoc's table formatting is much easier to read, write, and maintain, and AsciiDoc tables are more robust, supporting headers, captions, custom dimensions for tables/rows, and complex formatting within tables.

Some other benefits include:

• A single, standardized format where Markdown and ReStructuredText do not (in other words, there are no "flavors" like you have in Markdown).

• Concise and readable syntax.

• A more gradual learning curve that ReStructuredText (probably due to its consistency and excellent documentation).

• Superior styling options for your output.

• A superior toolchain to the other two markup languages.

• A rich set of built-in documentation features, so you rarely have to rely on third-party plugins.

AsciiDoc was designed from the ground up for technical documentation, whereas the other two get shoehorned into that role.

Having worked extensively with all three, I can't recommend AsciiDoc highly enough.

I agree. Having worked a lot with both, I think Elixir is by far the better language, especially for web programming.

I've worked with strongly typed languages and duck typed languages. I've also worked a lot with Go and Elixir. In my opinion, the tradeoff between the elegance of Elixir's actor-based functional style vs. Go's warty imperative style is more compelling than static typing vs. duck typing.

I love working with Elixir. Go is something I tolerate.

I hear you!

I quit doing engineering work for companies, but back when I did, I'd take some complex code I'd written to interviews. I tell the interviewers that I'm happy to step through my code and explain it during the interview, but that I wasn't interested in wasting hours of my weekend writing a werpderzle or answering gotcha questions.

Some companies agreed and I ended up working for them and some companies didn't, so I'd end the interview. In my experience, companies that over-complicate the interview process also over-complicate their day-to-day work, and I don't have any interest in working in that sort of environment.

I used to use tree explorers all the time, but once I discovered fuzzy-search file explorers, I never used a tree explorer again. It’s been too long for me to remember why I liked tree explorers before or why I stopped using them, so I’m curious, what are the benefits of a tree explorer over a fuzzy-search file explorer?

I’m not questioning the usefulness or validity of tree explorers. I’m just trying to see things from a different perspective.