Frontend automation has been getting pretty wild lately. 🫠 A few months ago, this comparison would...
So basically Claude at 20 buck sub is not much better than free. Chatgpt. It is pretty much shit. Gemini. It seems to have some reductions to its abilities in the last couple of months as well. The 20 buck price range used to have lots of good ais. Now they are all limited, downgraded. What would be the king in this price range? I have found myself using gemini ai pro with other ais as free on the top of that. submitted by /u/aluode [link] [留言]
Hi, I'm prepare for a phd in the US in medical AI, so I want to improve listening and speaking skills. I warry about admission interview, and I like discuss research. I find male friends because I have a girlfriend. I don't want to make her worry. I find the friends online firstly. Please feel free to contact me. submitted by /u/CrazyIndependent7436 [link] [留言]
Amazon Prime members will be able to buy July 29 tickets for Spider-Man: Brand New Day.
https://archive.ph/TNLUr
A hands-on knowledge-distillation project: Qwen2-VL-7B → 2B for UI-screenshot understanding, trained, evaluated and benchmarked end-to-end on an M4 Pro. 2.4× faster — and why the teacher lost on ROUGE-L.
submitted by /u/CatCognition [link] [留言]
Over the past few months, I've been working on a high-scale scraping pipeline to aggregate listings directly from company job boards and applicant tracking systems. Mapping over 100,000 distinct companies to their career pages turned out to be a massive engineering headache, but it's finally stable. The result is a unified database of more than 2 million active job postings, which I'm opening up to everyone for free. I am running daily delta refreshes to keep it current. Dataset Overview Scale: 2M+ active job listings across 100,000+ unique companies. Format: Parquet. (To keep storage costs to minimum) Core Fields: job_title, company_name, company_website, job_description, location, post_date, and the original tracking URL. For more detailed info check here . Update Cadence: Refreshed daily straight from the source. View the stats here . (Currently it contains only minimal stats, but I plan on improving it based on the comments) Why I Built This Finding a clean, scaled, and up-to-date job dataset is surprisingly difficult. Most available options are either heavily gatekept by expensive subscription APIs or restricted to a single job board like LinkedIn. By scraping the actual employer sites directly, this collection sidesteps the noise and captures a much cleaner cross-section of the live market. How to Access It I set up a dedicated project space where you can grab the data directly: Open Job data Let me know what kind of analysis or projects you end up running with it. If you have questions about the engineering architecture behind handling this scale, or ideas for specific fields you'd like to see enriched next, let's discuss in the comments. submitted by /u/Invicto_50 [link] [留言]
submitted by /u/r_retrohacking_mod2 [link] [留言]
I've been building out embedded reporting for b2b clients (i use next.js), and as our user base grows, the P95 latency is becoming a nightmare. Every time a user changes a date filter, it triggers a fresh compute spin-up on the warehouse. I’m currently refactoring the stack to put a universal semantic layer (in my case, cube core) between the frontend and the database. and the goal is to move all the logic, like multi-tenant row-level security (RLS) and complex joins, out of the React code itself and into a declarative modeling layer since I started, the biggest win (so far) is using pre-aggregations. now, instead of hitting raw tables, the API hits a warmed caching tier which is in the 'cubestore'. it feels more like querying a structured API than a database for those of you here who do high-concurrency analytics in SaaS, a question! are you just throwing more money at warehouse compute, are you moving toward this kind of decoupled architecture, what other best practices do you have? now trying to figure out if I should stick with this or just move everything to a huge ClickHouse instance and hope for the best submitted by /u/sivyh [link] [留言]
Inspiration Build a simple and modular technical documentation and blog. Build the website without using node/npm or any external frameworks(CSS, JS, icon, font). Only GoHugo normal binary + pageFind binary needed. Features [x] Responsive and adaptive layouts. [x] Support for light and dark modes. [x] Support for multiple documentation sets. [x] Support for a blog. [x] Implement a menu via Hugo configs. [x] Customizable sidebars using Hugo data templates. [x] Plug-and-play/ repeatable home page blocks using separate partials/ css/ data templates. [x] Integrate a search via Pagefind. [x] Inline SVG icons based on Google's Material Symbols GitHub Repo: https://github.com/dumindu/E25DX Example Docs: https://github.com/dumindu/E25DX/tree/gh-pages/example Example Live: https://dumindu.github.io/E25DX/ submitted by /u/dumindunuwan [link] [留言]
OpenAI calls for global action on youth AI safety, proposing an international institute to strengthen safeguards, standards, and opportunities for young people.
Why C Is Still the GOAT (And Why People Like Me End Up Hating C++) Disclaimer: This is a personal opinion from a developer who enjoys simple tools, simple languages, and simple debugging sessions. The Eternal Question Every few months, somebody asks: "Why are you still writing C in 2026?" My answer is always the same: Because C knows exactly what it is. No hidden magic. No surprise abstractions. No template metaprogramming black holes. No compiler errors longer than my source code. Just you, a compiler, and a Segmentation Fault waiting patiently around the corner. C Is Honest One thing I love about C is that it never pretends to protect me. If I allocate 8 bytes and write 16 bytes? Boom. If I dereference a bad pointer? Boom. If I forget to free memory? Boom (eventually). But here's the important part: I know exactly why I got cooked. The language didn't hide anything from me. C basically says: "Here's the loaded foot-gun. Try not to shoot yourself." And honestly? I respect that. Meanwhile in C++ C++ often feels like this: template < typename T > concept SomethingComplicated = requires ( T t ) { // 300 lines of magic }; Then the compiler responds with: error: instantiation of recursive template ... required from ... required from ... required from ... required from ... ...followed by 14 pages of diagnostics. At this point, I'm no longer debugging my code. I'm debugging the language itself. My Personal Villain Origin Story I started using Visual C++. You know. The gigantic Microsoft ecosystem. The IDE. The project files. The build settings. The mysterious compiler flags. Eventually I found myself spending more time fighting tools than writing software. And somewhere along the way, I started associating that frustration with C++ itself. Fair or unfair? Probably unfair. But emotions aren't always rational. Modern C++ Feels Like Three Languages Wearing a Trench Coat Old-school C++? Pretty understandable. Modern C++? Sometimes it feels like: C Object-Oriented C++ Template