https://nitter.cf/t.co/ljMzq5muQ9
Joined July 2007
- Tweets8.8K
- Following696
- Followers2.7K
- Likes1.8K
Pinned Tweet
bsky.app/profile/iamthefury.…
Bye y’all. See you on the other socials.
Jeff Hampton retweeted
Released Talkify 0.8.0 and Prompt Shaping with Apple's foundation models are here.
- We've Added Prompt Shaping by supporting Apples on device models. Turn it on in Settings > Prompt Shaping and the prompt you pick rewrites finished dictation through Apple's on-device model before it is inserted
- Three prompts are built in. tighten grammar, bullet my lists, remove filler words. Each shows what it does under its name. You can edit them or write your own
- Added a Try button to the prompt editor. Type a sample sentence, press Try, and see what the model does with it before you rely on it.
- Shaping is off by default.
- Shaping runs before translation, so a translated session cleans up your words and then translates them.
Thanks for contributions
@jhampton
usetalkify.app
github.com/tornikegomareli/T…
I wanted voice dictation on macOS to feel instant and native, and I built Talkify an 8.2 MB macOS dictation app with 123 ms median release-to-text latency. It was the fastest of five apps tested ahead of superwhisper, voiceink, wispr flow and macwhisper.
It lives in your notch and have beautiful shader animations and different kind of customizations.
Talkify is built on top of Apple’s SpeechAnalyzer using system-managed speech models to transcribe audio entirely on-device, its free and open source.
usetalkify.app
github.com/tornikegomareli/T…
Jeff Hampton retweeted
I wanted voice dictation on macOS to feel instant and native, and I built Talkify an 8.2 MB macOS dictation app with 123 ms median release-to-text latency. It was the fastest of five apps tested ahead of superwhisper, voiceink, wispr flow and macwhisper.
It lives in your notch and have beautiful shader animations and different kind of customizations.
Talkify is built on top of Apple’s SpeechAnalyzer using system-managed speech models to transcribe audio entirely on-device, its free and open source.
usetalkify.app
github.com/tornikegomareli/T…
Jeff Hampton retweeted
6. If you haven’t tried @tan_stack start, there’s no better time than right now
tanstack.com/start/latest/do…
Jeff Hampton retweeted
For those looking for an alternative
nitter.cf/amasad/status/19727064…
Jeff Hampton retweeted
idea: build a better file browser
result: liminal froggy OS
my gripe with all digital file management is theres no sense of spatial memory
when i studied for tests i remembered the shape and structure of my notes and that pointed me to where things were (see memory palace) modern file systems feel like a magic soup where you whisper your best guess at the name into the void
someone please fix this
My wife and I are selling the business we built from scratch. If you've ever dreamed of owning your own retail business, the details are here: bizbuysell.com/Business-Oppo…
Jeff Hampton retweeted
In the AR, overlays can be interactive.
Sorry about the shakey screen.
Always #buildinpublic
Jeff Hampton retweeted
A rainy day in Brooklyn led to a new project.
An AR pinout overlay using the Metro M7 board from Adafruit. This was built in SwiftUI and UIViewRepresentable to merge UIKit views. It tracks well if I say so myself!
Jeff Hampton retweeted
AI-first pull request reviewer with context-aware feedback, line-by-line code suggestions, and real-time chat.
Jeff Hampton retweeted
WE ARE GIVING AWAY A CYBERTRUCK
ACTUALLY A CYBERBEAST
REPOST TO ENTER
FOLLOW SO WE CAN DM YOU
NO PURCHASE NECESSARY. TERMS: stickermule.com/rules/cybert…
Jeff Hampton retweeted
A bunch of total fabrications flying around about React Lua from people such as rush to stream, they don’t both to ask questions to the people who built the thing. First, React Server Components could’ve been ported and absolutely make sense, we didn’t do purely for time. Anyone could uncomment the RSC code in the port and bring the tests over, or roll forward changes commit by commit from upstream. Upgrading to React 18/19 is also incremental work, and I’m sure folks at @ThisDotLabs would be up for that work if someone wanted to fund it.
Jeff Hampton retweeted
It's extremely unfunny now
But within 5 years it will be as funny as the real thing
Humor is a sign of intelligence, so I asked Claude-Sonnet-3.5 to absolutely COOK GPT-4o.
Then I put the results into a @DaveChappelle deepfake.
The result is damn jarring... See for yourself:
Jeff Hampton retweeted
The first playing with this idea,
@jhampton and I did a hackathon to use an LLM to do the translation. It’s not a straight syntax tree conversion, there’s some semantic things that are extremely context-dependent: like when to use metatables or IIFE to achieve something versus some other mechanism. It would be Very Interesting to feed JS-to-Lua’s commit history to a coding LLM and then ask it to add the next feature (along with test) and see what happens, though! Of course, anyone wanting engineers to do JS-to-Lua work should call @ThisDotLabs , as they did 100% of that transpiler work and know more about the ins and outs of deep Roblox Lua development than just about anyone else.
@SodaStreamUSA what do I do about an empty refill that I just exchanged? I cracked the seal and it’s completely empty.
Jeff Hampton retweeted
I’m at @RenderATL with my engineering partner @callstackio . We’ll be giving demos of @reactnative and @babylonjs @AppleVisionPro , talking about the new features in visionOS 2.0 that was released yesterday, and generally talking about the mechanics of building a Mixed Reality product business! Come say hi!
Jeff Hampton retweeted
Consider the following async/await.
Pretty straight forward, right? Sure.
Here's what I see:
1. What happens when a user clicks this button again before the first async handler is done?
2. What happens if both awaits in the first call succeed, but the second await in the second call fails or hangs?
3. What happens if the second await in the first call is a lot slower than both awaits in the second call?
4. If we add some sort of cancellation to this, how do we manage that? It has to be passed to each promise-returning function, and as promises aren't really cancellable, it must reject in order to interrupt the async function processing....
In short, async/await is lipstick on a pig. The pig being asynchronous programming in general.
Async programming is NEVER easy. It's NEVER straightforward.
