paperplatter

7 ms·

31.
by paperplatter 2y ago
I think that was it. There was also something about tuples inside of dictionaries that Swift 1 or 2's compiler segfaulted on.
32.
by paperplatter 2y ago
I started using RN when I had 0 web skills and didn't know JS. Everything from making a simple button to hooking up the model was easier to me in RN from day 1 than the native iOS way that I'd been using for years.
33.
by paperplatter 2y ago
The issue here isn't ASCII vs unicode, it's specifically symbols that are composed of multiple unicode codepoints.
34.
by paperplatter 2y ago
Computed properties are annoying too. More importantly, they're one more inconsequential thing for SWEs to argue over in code review.
35.
by paperplatter 2y ago
Also, is anyone familiar with the weirdness with tuples in Swift? All I remember is they never worked the way I expected, and for some reason something in our code specifically worked for tuples up to size 5.
36.
by paperplatter 2y ago
I'm fine with either approach as long as it's consistent. Practical Swift code will have a few "inout"s sprinkled around, wherever someone happened to pass in a struct (like array) instead of an object (like NSArray). An
37.
by paperplatter 2y ago
I've seriously used Erlang for a while, and Haskell looks kinda similar. Ingenious ideas there, cool features, but in the end it's cumbersome to use. So I can see why these are niche and wouldn't consider them next to big one
38.
by paperplatter 2y ago
I'm actually surprised at this because while UIKit is hard to use, at least it's fast. Though I remember the concurrency model being confusing, so you could accidentally block your UI thread.
39.
by paperplatter 2y ago
Swift was designed around emojis it seems. First page in the manual shows how you can use emojis as variable names. I get why Apple wants to be clear how there are different ways to index into strings (even if this is motivated 99% by emoji
40.
by paperplatter 2y ago
The thing is, each string-related answer ended up extending it with some methods that everyone wanted it to have in the first place, and the top-voted comments are like "why do we have to do this." It also shouldn't have requ
41.
by paperplatter 2y ago
If Rust is one, yeah I have to fight that compiler but it's because it's doing its job and not letting me do invalid things. Not because the compiler has some feature "not yet implemented" or has bugs.
42.
by paperplatter 2y ago
Sorta, but it's not as easy as they make it sound. And people will use RN even for iPhone-first stuff.
43.
by paperplatter 2y ago
Yeah there's a reason people go to all that effort with React Native to avoid writing Swift code or dealing with Apple's UI frameworks, and it's actually a reasonable approach for the majority of apps.
44.
by paperplatter 2y ago
I use C++ at work but am glad I didn't learn it before. Yes it's a good language for what it's made for, but there are so many features that anywhere you work, you will use it differently from how you used it before. Better t
45.
by paperplatter 2y ago
If I were new to Swift and saw how complicated and version-specific the Stackoverflow answers* are for things that are super simple in other languages, I wouldn't expect things to get much easier from there. And that instinct would be
46.
by paperplatter 2y ago
Swift is the only language where I've had to fight the compiler to do its job. In earlier versions like 1.x and 2.x, it would often segfault. By 3.x it was still really slow to build. I regretted moving a project off ObjC back then. I
47.
by paperplatter 2y ago
That's neat. It should be just as easy in theory to generate tests from the OpenAPI spec, but idk what tooling there is.
48.
by paperplatter 2y ago
I can see that, but plate armor was prominent in the later middle ages too, pre-Renaissance. And D&D has no gunpowder weapons, which were starting to be common in the Renaissance. Then again a lot of "medieval" movies/TV&
49.
by paperplatter 2y ago
No, D&D is definitely set in medieval Europe except with magic added, and the mythical creatures are based on European fairy tales (albeit ones before the medieval era). The weapons are also medieval era specifically, with types of swor
50.
by paperplatter 2y ago
If by scripting monkey friendly you mean Javascript or Python, nah I'm going to use that.
51.
by paperplatter 2y ago
There's probably a library function that's so annoying to call that people don't bother. Like you gotta first convert the NSString to an NSPath, acquire your library path using some singleton, then construct NSFileHandle (don
52.
by paperplatter 2y ago
Step 1 is a crazy vulnerability on its own. How did Apple not consider this? > The attacker can exploit this to conduct a successful directory traversal attack by setting an arbitrary path to a file in the ATTACH section with: “FILENAME=
53.
by paperplatter 2y ago
The way I understand it now, they attach an invite to an email that you don't even read, but it shows up on your calendar. Is it too much effort to open the attachment yourself? Normally you think twice about opening an attachment from
54.
by paperplatter 2y ago
I think this isn't specific to iCloud, just in general invites are automatically picked up from emails. Calendar invites have long been a source of spam, so I'm not surprised there's also a vulnerability.
55.
by paperplatter 2y ago
I'd avoid having separate services share a DB. Besides the overhead, you get scary hidden dependencies that way. If this approach is considered not micro but rather an in-between, the article should mention it as an option.
56.
by paperplatter 2y ago
Makes sense, since Google uses a monorepo (google3).
57.
by paperplatter 2y ago
Do FAANG engineers normally advocate for more services instead of fewer? I haven't gotten that impression.
58.
by paperplatter 2y ago
I think the assumption here is that "microservices" means each team is dealing with lots of services. Sometimes it's like that. But if you go by the "one service <=> one database" rule of thumb, there will pro
59.
by paperplatter 2y ago
There would be a mix of versions, managed via branches. The part about debuggability sounded appealing at first, but if the multiple services you want to run are truly that hard to spin up locally, it won't be any easier as a monorepo.
60.
by paperplatter 2y ago
"To get similar characteristics from a monolith, developers need: Incremental build systems Incremental testing frameworks Branch management tooling Code isolation enforcement Database isolation enforcement&qu

More ›