I run the same config but it tends to fly through those commands on the weekends, very noticeable difference. I wouldn’t be surprised that the subscription users have a (much) lower priority.
That said I don’t go beyond 70% of my weekly limit so there’s that.
This is very unrelated but I worry about posts like these.
HN is a great place to get genuine thoughtful discussions compared to a big portion of the rest of the internet. Reddit used to be the place for finding genuine experiences for products with subreddits like buyitforlife (or more specific) but now these and other subreddits are filled with bots and marketeers promoting what they sell and hammering their competition in the same thread.
Some bots are already here but I fear when the marketeers come.
If you spot one flag it and mail hn@ycombinator.com , Dan & Tom usually act pretty quickly on confirmed shills. But don't comment in the threads to accuse someone of being a shill, that's explicitly against the guidelines, and that's because it isn't rare for people to simply get it wrong, besides it would pollute the threads.
It used to be Hola VPN which would let you use someone else’s connection and in the same way someone could use yours which was communicated transparently, that same hola client would also route business users. Im sure many other free VPN clients do the same thing nowadays.
From what I can read Swift gives you a stack trace which is good. At the moment I’m using Go where that stack is only generated where the panic is triggered, which could be much higher up. Makes it a lot more unwieldy to figure out where an error happens because everyone uses:
When you call code that can throw (return an error via the special return path) you either have to handle it or make the enclosing context also throwing.
Assuming `canThrow()`, a function that might throw an `Error` type:
func canThrow() throws {
...
}
Call canThrow(), don't handle errors, just rethrow them
func mightThrow() throws {
try canThrow() // errors thrown from here will be thrown out of `mightThrow()`
...
}
Alternatively, catch the errors and handle them as you wish:
func mightThrow() throws {
do {
try canThrow()
} catch {
...handle error here
...or `throw` another Error type of your choosing
}
...
}
There are a few more ways to handle throwing calls.. For example
- `try?` (ignore error result, pretend result was `nil`)
Swift doesn't capture a stack trace in the `Error` object, but Xcode can break when an error is thrown if you set a “Swift Error Breakpoint”, and the debugger will show you the stack trace. Under the hood it just sets breakpoints on the runtime functions `swift_willThrow` and `swift_willThrowTypedImpl`.
Might not be the best fix but other than disabling memory I changed the setting ‘ChatGPT personality’ to ‘Robot’ and I’ve always had straight to the point answers (so far).
> The total wall clock time for the build was measured. The smaller the better. I always did one build to prime the caches and discarded the first result.
- LLM's are too limited in capabilities and make too many mistakes
- We're still in the DOS era of LLM's
I'm leaning more towards the the 2nd, but in either case pandora's box has been opened and you can already see the effects of the direction our civilization is moving towards with this technology.
It has the same name, not the same functionality. I am not a downvoter... but it's probably because reading a few sentences of this blog post would reveal what it is.
It wasn't even a criticism, just an observation for anyone else who was thinking the same or was interested in another popular project with a similar name (and seemingly similar functions? didn't look too hard).
Naming things is hard and we all kinda share one global tech namespace, so this is gonna inevitably happen.
That said I don’t go beyond 70% of my weekly limit so there’s that.