Technology Mixer (tech stuff, software developmen, AI, LLM, blockchain)
1 subscriber
22 photos
1 video
11 links
Stuff about software, blockchain development, AI, LLM and other cool IT things.

πŸ‘πŸ»: Rust, Kotlin, Python, Linux.
πŸ‘ŽπŸΏ: Windows, Javascript, Ruby, PHP, .NET, Go, MacOs.
Download Telegram
🐍 Python: I'm slow but I have so many libraries
🐭 Go: I'm fast but I make you write a lot of boilerplate for simple things
πŸ¦€ Rust: I'm faster but have you seen my error messages
β˜•οΈ Java: I've could've been faster without Spring and other bloatware frameworks
Meta's AI glasses πŸ‘“ failed TWICE during live demo at Connect 2025. πŸ€¦πŸ»β€β™‚οΈ The main mistake here was a confidence in live demo success with no backup plan.

βœ‹πŸ»But nevertheless I think that hardware behind all this is awesome. Core software worked well so it was more likely connectivity issues. πŸ‘πŸ»

And one more think. All of it was real.
Want to crush it as a #blockchain dev? Start learning Solidity!
It's the key language powering #EVM chains like #Ethereum, Tron, Polygon, Binance Smart Chain, Avalanche, Arbitrum, Optimism, Fantom, and beyond. Master one skill, unlock many job opportunities.
For any RoR & Ruby developer arguments you can confidentely say that PHP had it before. I'm pretty shure it will be true >= 90% of all cases.
I'm using #Linux more than 20 years as a main OS and I know it flaws. But now looking at what Windows 11 become I'm starting to believe that Linux really can fix it 🐧
πŸ—„οΈDatabase Types You Should Know in 2025

There’s no such thing as a one-size-fits-all database anymore. Modern applications rely on multiple database types, from real-time analytics to vector search for AI. Knowing which type to use can make or break your system’s performance.
About AI for software developers.
It definitely capable of doing some primitive work or giving you a hint faster than web search. But when it comes to something complex or safety critical I would not put my trust in it.
πŸ¦€ The #Rust experiment in #Linux is officially over - and it's a success! πŸ˜‰
Rust has graduated to being a core part of the kernel.
Local API mocking server & πŸ¦€ Rust unit test library with β›© Jinja templates and 🌿 Rhai scripting language.

Could be useful for:
- πŸ‘¨πŸ»β€πŸ’» local development to do not run/build other services & call external APIs
- πŸ’»πŸ› βš™οΈ integration tests if 3rd party API provider suck/stuck/etc
- πŸ’»πŸ‹πŸ»β€β™‚οΈ load tests - when deployed alongside your application Apate should respond fast, so no need to take external API delays into account
- to write πŸ¦€ rust unit tests with complete in-out flow

#rust #rustlang #rhai #api #mocking #tests

https://github.com/rustrum/apate
New WhatsApp for Windows consume 1.5Gb of RAM instead of 0.2Gb if compared to the old one πŸ€¦πŸΌβ€β™‚οΈ.
Can you guess why?
Pin / Unpin in async Rust 101 πŸ“Œ

Here’s the mental model to help understand Pin/Unpin:

Rust async is basically β€œa function that turns into a state machine.”
And that state machine lives somewhere in memory.

When you .await, the future can pause and resume later - meaning it must remember where it was and what it was holding onto.

Sometimes that β€œwhat it was holding onto” includes references into itself.

Why you usually don’t see Pin in day-to-day async Rust?

Because async fn hides it.

When you write:

let fut = my_async_fn();

that fut is an anonymous future type, and Rust/your executor will ensure it’s pinned correctly when it’s polled.

If you use tokio::spawn(fut), Tokio will pin it internally (usually by putting it on the heap).

So you only hit Pin when you:

1. build your own futures
2. store futures in structs/enums
3. want self-referential patterns
4. do low-level async runtime stuff
πŸ›‘ WARNING: CVE-2025-20393 is rated 10.0, with no patch available.

Cisco confirmed active exploitation of an AsyncOS zero-day by a China-linked APT.

The flaw allows root-level command execution on affected email security appliances and enables attackers to establish persistence.

πŸ”— Details and mitigations β†’ https://thehackernews.com/2025/12/cisco-warns-of-active-attacks.html?m=1
So... Postgres is now basically a search engine?

pg_textsearch was just open sourced. It enables BM25 to search your database.... massive upgrade for key word search.

Google uses BM25 in their search engine.

if you're already on Postgres, you can now skip the whole "sync your data to Elasticsearch" stuff for search.

https://github.com/timescale/pg_textsearch
MongoBleed is a vulnerability affecting all MongoDB versions from 2017 to... today.

The exploit is simple. It's a buffer over read bug due to compression. Here's how it works πŸ‘‡

Clients can send compressed requests to MongoDB.

The client helpfully includes the uncompressed size of the message so the server knows exactly how much memory to allocate when decompressing.

The server allocates a memory buffer with the given space. Due to how memory management and garbage collection in programs work, this allocated memory may already contain sensitive information that was copied earlier and is considered garbage now (eg because it's unreferenced).

The exploit sends a badly-formatted BSON message. The server fails to parse it, and "helpfully" returns an error message containing the invalid message. The invalid message can be that whole 1MB block of foreign data.
This is one of the biggest problems in software development today. And the worst thing is that newcomers are taught these N layers of abstraction as something perfect that will solve all problems.