imheresamir

The investors who sold shares to the company did so at the then-current publicly traded share price. I bet they wish they didn't since the stock value increased after the sale. These investors who sold did not benefit from the sale any more than they would have selling on the open market in a non-buyback situation. Hope that makes it clear!

Can you answer the question "who gets money literally put in their pockets as a result of a stock buyback?"

Hint: the answer is... no one. Investors who held see the value of their holdings increase, again, different from "cash in your pocket"

You said:

> Who do you think they are buying the shares from? It literally directly puts money in the pockets of investors.

He's trying to explain to you why stock buybacks don't "literally directly put money in the pockets of investors". If your shares are sold back to the company as part of the buyback you are 1) no longer an investor obviously, and 2) have not realized any gains as a result of the buyback. Investors who did not sell see their shares appreciate, which is different from "putting money in their pockets"

Cashing in social capital in retaliation for their partner getting fired?

Firmware/Backend Engineer/Rust Afficianado/Puzzle Hunter looking for a challenge

Apparently, data acquisition firmware I wrote is running on instruments in three different Covid-19 vaccine production pipelines

Location: Santa Barbara, CA

Remote: Yes

Willing to relocate: Yes

Technologies:

• Languages: C++, Python, C, Rust, TypeScript/JavaScript, HTML/CSS, Bash, Assembler (8086/ARM/RISC-V), VHDL (Xilinx ISE WebPack), SQL, Java, Go, nMigen

• Digital Protocols: I2C, SPI, UART, USB. Comfortable with oscilloscope/logic analyzer, USB packet analyzer, Wireshark

• Web Technologies: React, MobX, Electron, Vue.js

• Database: Sqlite3, Postgres, MS SQL Server

• Mobile/Embedded Platforms: Embedded Linux including Raspberry Pi (and other Linux capable ARM-based SBCs), Arduino, Bare-metal Rust and C, RTIC, FreeRTOS, Android

• Microcontrollers: STM32 (ARM and RISC-V clones), ATSAMD51, ESP8266, Kendryte K210 (RISC-V), SiFive E310 (RISC-V), AVR, STM8, various FPGA-based RISC-V soft-CPU cores

    ◦ Developed first embedded Rust Peripheral Access Crate (PAC) for RISC-V based ESP32-C3

• Infrastructure & Tooling: Docker, Illumos LX Zones and bhyve, OpenAPI

• Reverse Engineering: Comfortable reverse engineering network protocols using Wireshark, binary analysis using IDA Pro and Ghidra, familiar with strace, dtrace, truss

Résumé/CV: https://drive.google.com/file/d/1ApAmO9IWv32D2ikwU2Zb9qRshcO...

Email: [email protected]

Updated, thank you.

Have you found the TRM yet? I really like the idea of this chip but the released documentation for it is woefully incomplete.

Is that not what the author is referring to? From the readme of his LiteDIP project[1]: "Plug-and-play LiteX-based IP blocks enabling the creation of generic Linux drivers. Design your FPGA-based SoC with them and get a (potentially upstream-able) driver for it instantly!"

[1]: https://gitlab.freedesktop.org/mupuf/litedip/

Could you provide a source for this? Just curious.

> A few community members have been working on a RethinkDB integration with Meteor and Volt, and we expect robust integrations to become available in the coming months.

If I'm understanding correctly, RethinkDB could be a drop in replacement for mongodb? What are the benefits to this replacement in the context of Meteor?