anilgulecha

I built a harness in the cloud with slack like interface for this, allowing multiple people to join. It allows chat members to tag action items, work on files and sync to GitHub. My team uses it to coordinate on our task and teM context together, setup meetings which are auto transcripted and ingested into the attached wiki, and connect to calendar to setup meetings. Built it for our needs.

Didn't really consider putting it out in public. Is there a viable product out of this? How much would you pay.

Camera app should negate the need. most pictures are of people and scenary, and 99.99% of the time the intent is to take the photo in the right order.

Simple totally offline ONNX models exist, whcih should make it trivial to categorize the right orientation. Acceleometer/magnetometer can feed this, but should not be the default.

Just do this and avoid the hassle of rotating at all!

is composer 2.5 that good at that pricepoint? Seems like the gemini flash playbook of trying to get most bang for the buck.

I understand the frustration (I'm an avid fdroid user across many many devices). But this article comes off as childish with the virus/trojan/"malware vendor".

With such an article, many (including perhaps google) get the ammo to disregard what fdroid says, by branding them as childish/not to be taken seriously. for eg: no reputable news org is going to post this.

PS: https://keepandroidopen.org/ is better done.

We can get creative. quick ideas: Send it by printed post. pass it around people to people. an email needs to be added in with some process, and can only get one TXT update value a week.

Many ways of adding friction to obtaining the updatable value - which a human owning a domain would be happy to do, but a squatter would not want to.

Hence the "in the first year or two". Some more human effort to showcase proof early on, then the domain is solidified for you like iwth any other registrar. This is something like captcha/bcrypt - a single instance isn't a burden, but doing it at scale is costly.

You cannot transfer ownership killing any value you added

I think this is by design. The domain should be for personal use - hence free.

The "one free domain per person" isn't the interesting part really - that will be hard to police unless domain name is a function of ID proof (avoids squatting).

0) The actual intersting part of a new TLD can be growing reputation by post-facto taking away a domain without recourse in case of squatting. Instead of adversarial takedowns (which produce false positives as noted), let anyone challenge an inactive domain in the first year or two.

1) If they can figure out a mechanism for moving a domain from "assigned" -> "squatted".

2) Domain must match (or derive from) a verified identity - e.g. your domain is a hash/slug of your government ID. Makes squatting structurally impossible because you can't claim someone else's name / gov (Sign in with passkeys linked to a national ID).

3) Proof of human effort, reduced with time - require periodic renewal with proof-of-use (DNS TXt updates, through a flow hard to automate).

4) Kill speculative market - domains are non-sellable and non-transferable - always go back to the free pool, and stay there for 30 days mandatorily.

Some mix of these could be the right structure for a trule high-reputation, free domain.

The author should call out size of binaries (compiled and generated), the interpreter as well since that's teh selling point. if it's tiny from memory requiremetns , shoudl also call out the same, potentially benchmarking against similar (luajit?).

No per-request billing, portable devops - easier multicloud, known semantics (env variables, entrypoint, websocket lifecycle).

If eastdakota/jgc are here.

- simply expose containers to the world directly - without having to go via workers.

- You have other amazing parts of the stack anyway (D1, durable objects, a great object store). These aren't considered "lockin".

- workers is "lockin" - not similar enough to lambda/cloud functions and so becomes CF specific.

Not having a simple container based compute piece has made me hesitate in taking up CF. (Fly or firebase won out)

translation.

It's not technically a translation, it's a re-implementation, with test suites acting as the destination. If it was a file by file translation your argument would have been valid.

We believe it would be good for the world to have the option to slow or temporarily pause frontier AI development to enable societal structures and alignment research to keep up with the advance of the technology. The Anthropic Institute will conduct research—in collaboration with many others—and take actions to help build the systems that a credible slowdown or pause would require.

Interesting - they're commiting to kickoff policy conventions to organize a world-slowdown of frontier LLM building. If they actually are able to crack it, this will give a much needed breather IMO. As exciting as the last ~6 months have been, there's some bigger questions to go answer now.

Disagree is such a loose/wimpy study. Add in a grounded/expected response, and then it becomes a better benchmark (because it'll force the author to actually think about choices presented to the LLM).

IMO, I read 2 faulty assumptions:

1) That LLM/Agents are being pushed and not adopted. I see plenty of deep adoption by junior folks.

2) The unit economics don't work out. From the details on every model so far - each model is wildly profitable over it's amotized time-frame. It's just that money is used upfront for the next model, and each next model is significantly more costly to train. The best case argument instead is - this will not last and we'll pour more on some models, than see in it's revenue.

I think realistically these form the core of the thesis, and IMO, and hence it's conclusions are a bit off the mark.

Rubbish. The license change was the reason for the fork of community, and people switching. Quality was never cited as the issue.

It is of course a multiplier. The worries are:

- Lesser overall engineers needed -> lesser demand of human engineers -> lower compensations

- insufficient training at junior levels.

- longer time to productive human engineering skill.

These are playing out right now, and a concern for all engineers in the industry. IronMan amplification don't address the above

I have anosmia, triggered by AERD/polyps. I have been mostly without the sense for the past ~12 years, but int eh past year have had bouts of smell again, via a doc who finally diagnosed AERD, and suggested steroid intervention + mepolizumab.

What a blast from the past. Couple decades ago I had submitted my first bit to this place.

https://github.com/Planet-Source-Code/anil-gulecha-bat-man-b...

VB6: What made a generation fall in love with programming.

IMO, not too many people are being discovered by substack. Twitter and other social media is where you have to have conversations to slowly build up your subscriber base.

(again)

I can completely empathize - sometimes some problems never leave us.. like that piece of food stuck b/w teeth. There's a force within us asking us to right that problem in the world.

All the best to your project.

Looking forward to the release. There's some DR benchmarks, which can you also run BTW.

the first is deep researsh like tool?

Well, what we're seeing the past few months is that natural language does - at least enough to build code and tests.

I think the industry is moving to English as the programming language, and specifications-context-tdd as the framework for building software.

Many find it distasteful, and many finding liberating. I think it's broadly correlates with how they feel about expressing themselves in english vs say C++.

As a side question, is there anyone who's using LLMs primarily in non-english mode to program? I suspect there's quite a few people using mandarin, but can someone share first-hand account.

I mean that's already happened. Everyone is expected to be a manager of agents. Anyone not doing this is programming for hobby.

Interesting project.

In a potential modern cloud, having a globally named primitives (computer, store, messaging) can unlock very wider applications. Have you come across any such?

I think this is the wrong path in LLM and SWE optimizations:

1) Programming language training happens by volume, and the amount of JS/TS/python out there, and the rate it's growing at - is causing a training effects loop, which means for a few generations of models, these will be the best performing languages. Will be hard for a contender to spin up.

2) At some point, if we plateau on productivity - then efficiency improvements will happen, which will open a door for programming languages that maintains productivity, but is 10x cheaper on cost.

3) I think more immediate gains are at the cloud level. IMO, one of the reasons Google cloud is performing better(along with firebase) is much better overall CLI experience, leading to a pleasurable experience developing against it. This part of the market is ripe - whoever builds a most LLM friendly cloud has a shot of shooting up. Hence projects like exe.dev, and whatever cloudflare and vercel are trying. It would be good to have some shakeup in the cloud world.

Anyway, this is where my thoughts are currently.

I thought it would be an informative discussion to have to apply these rubrics to LLM and AI use coming in across domains, in the context of Freedom of Refusal / Reversal.

Crystal was always something I looked at ~5 yrs ago - alongside golang and rust. But it would out of the new cycles. Looks like they solved for 2 big things in these years: fast development cycles and windows support.

Very cool. I wonder how it stacks up against golang for production apps. Anyone comment?

That would be valuable if there's a commitment to never have a non-opensource offering under GoModel? If so, you can document it in the repo.