#Either

The 🫠 ᴘʀᴇᴛᴛʏ BBC Radio 3 🎶 #NowPlaying Bot

@bbc3musicbot.bsky.social

1 month ago

AMBASSEL Either/Orchestra · Ethiopiques 32: Nalbandian L'Ethiopien The Ethiopian · Song · 2025

🇺🇦 #NowPlaying on BBC #Radio3's #RoundMidnight

Either/Orchestra:
🎵 AMBASSEL

#BBCRadio3 #Either #Orchestra

▶️ 🪄 Automagic 🔊 show 📻 playlist on Spotify
▶️ Track on #Spotify:

0 0 0 0

$LeGoûterⓂ️♾️ℹ️ ¯\_(ツ)_/¯$

LeGoûterⓂ️♾️ℹ️ ¯\_(ツ)_/¯

@legoutervivre111.bsky.social

1 month ago

More #FIFA boycotts pls ty pls

youtu.be/JjCaDz6BweI?...

#Europe #monde

the governing body has debased and disenfranchised #football soccer fans

EVERYWHERE

I'll take a prize. It wont make it easier for u here #either

#remixthenews #musicchallenge

2 0 0 0

Malki

@blackmalki.bsky.social

1 month ago

a man is sitting in a lotus position in front of a large eye in the sky . ALT: a man is sitting in a lotus position in front of a large eye in the sky .

Everyone does not adhere to the #same laws. #Newtonian laws may not apply to #quantum realms as #spiritual laws supersede physical law or the law of the #state. The #leaders of this world follow neither 😒yet will be unable to escape #either.

0 0 0 0

Melz

@l3tm3live.bsky.social

1 month ago

📹 #Either | #Nas

#FuckJayZ

4 0 0 0

The 🫠 ᴘʀᴇᴛᴛʏ KEXP 🎶 #NowPlaying Bot

@kexpmusicbot.bsky.social

1 month ago

🇺🇦 #NowPlaying on #KEXP's #WoPop

Either/Orchestra:
🎵 L'Algerie: Gnawa loops

#Either #Orchestra

▶️ 🪄 Automagic 🔊 show 📻 playlist on Spotify

0 0 0 0

Nicolas Fränkel 🇪🇺🇺🇦🇬🇪

@frankel.ch

1 month ago

#Arrow's #Either: The #Kotlin Chapter of our Scary Words Saga

https://cekrem.github.io

#FunctionalProgramming

0 0 0 0

Miss Kitty 🌈🌈🌈

@misskitty.art

1 month ago

#Older people #still #care, but we have that #dying to #prepare for. You do not want to #hear about #that #either, but mine is a #mature outlook. My #life #continues past this flesh, and at this point, even if I know more than you, I know nothing. It #requires my #attention if you do not.

0 0 0 0

Nicolas Fränkel 🇪🇺🇺🇦🇬🇪

@frankel.ch

1 month ago

From #Either to Raise

https://arrow-kt.io/lear

#Kotlin #Arrow #FP

3 1 0 0

Opperman Report

@oppermanreport.bsky.social

2 months ago

He's Either A Cop or a Snitch with a Well Trimmed Mustache He's Either A Cop or a Snitch with a Well Trimmed Mustache

📣 New Podcast! "He's Either A Cop or a Snitch with a Well Trimmed Mustache" on @Spreaker #a #cop #either #hes #mustache #or #snitch #trimmed #well #with

0 0 0 0

The 🫠 ᴘʀᴇᴛᴛʏ BBC 6Music 🎶 #NowPlaying Bot - Radio 6

@bbc6musicbot.bsky.social

3 months ago

Amhara Rumba, by ETHIOPIQUES SERIES from the album Nalbandian The Ethiopian & Either/Orchestra

🇺🇦 #NowPlaying on #BBC6Music's #NewMusicFix

Either/Orchestra:
🎵 Amhara Rumba

#6music #Either #Orchestra

▶️ 🪄 Automagic 🔊 show 📻 playlist on Spotify

▶️ Song/Cover on #Bandcamp:

1 0 0 0

Cielle_Slime

@cielleslime.bsky.social

3 months ago

Hey two saturdays in a row? Am I getting consistent? what? the updates been out for 3 days?... oh...
WELL if you wana see my take on the new Warframe: The Old Peace come check out either of my streams!

#slime #vtuber #warframe #stream #twitch #youtube #either #adhd #mmolite #weekendstreamer

2 1 1 0

DragonSusie

@dragonsusie.bsky.social

3 months ago

I'm #Late #Again for #MutualMonday, #Either #Before or #After #Midnight, #Depending on #Location ( #Almost 3am #Here). But, we #Prevail.

#Help #HelpSky #FundSky #MutualAid #MA #MABoost #SignalBoost #Solidarity #KeepFolksAlive #HelpFolksLive #HelpFolksLive2025

7 2 0 0

@hesamiar.bsky.social

4 months ago

This #administration is telling the #American people they can #either have #food or #healthcare not both. Actually they don’t want to give you either one. Are you listening my fellow Americans? Your #government doesn’t give a shit about you. Maybe now you’ll do something about it? #resist #rise

0 0 0 0

ricardodominguez.net

@rrdominguez.bsky.social

4 months ago

#Rebranded #HomeDeport #Not #Giving #My #Dinero #You #Shouldn't #Either #Amigos

0 0 0 0

Miss Kitty 🌈🌈🌈

@misskitty.art

4 months ago

Same. Keep on postin'!
#MAGA / #NotMAGA #either
Somebody's #baby. Somebody's #mother. Somebody's #son #Snatched, #sent, #dead?? Has to end. The #ORDER part #Trump threw out because HE IS THE #LAW, out of his mouth not mine. He is plainly #irremediable. That was code so #VANCE couldn't understand.

1 0 0 0

Creaftar

@creaftar.com

7 months ago

Illustrative photo of call to play (generated with artificial intelligence) - Creaftar

🧠 Crossword challenge! Can you solve either?

🔗 - https://creaftar.com/en-us/play?cr=aUp3eVdFWZmHWpc4bClm

#fun #crosswordsolver #wordpuzzle #either

0 0 0 0

Kai25

@kai-25.bsky.social

8 months ago

Does #anyone know who #he is? I love a #dude with an #accent and his #cock isn’t #bad #either.

5 1 0 0

Puffer

@culturesurfer.bsky.social

9 months ago

a man with a beard and mustache says " it could go either way " ALT: a man with a beard and mustache says " it could go either way "

If you do #not support Ukraine, this 'Tech-Hub' #falls under Russia. Russia wants to own the whole landmass of Ukraine.

#Either support #or not. Then your future enemies...

Do you see the problem?

2 0 0 1

@gamingvideos.bsky.social

9 months ago

I invented a chair that either teleports you or brutally kills you This game is called Garry's Mod and we're playing a gamemode called DarkRP. The Oddlaws DarkRP even

I invented a chair that either teleports you or brutally kills you
This game is called Garry's Mod and we're playing a gamemode called DarkRP.

The Oddlaws DarkRP event was a private server set up a... #teleports #that #brutally #invented #either #gaming

0 0 0 0

Creaftar

@creaftar.com

9 months ago

Illustrative photo of call to play (generated with artificial intelligence) - Creaftar

Take the challenge of either!

🔗 - creaftar.web.app/play

#mentalexercise #wordgame #either

0 0 0 0

Calvin D. Wills, Jr.

@calvin-wills-jr.bsky.social

10 months ago

It doesn’t have to be an #either / #or #choice. There are many #policy #areas where we, as #pro-#democracy #advocates, can #resist. We have the #numbers to #fight on more than one #front. #Time to #understand we are working to #save #USA’s #soul & we must engage in many #battles to #win this #war!

2 0 0 0

Creaftar

@creaftar.com

11 months ago

Illustrative photo of call to play (generated with artificial intelligence) - Creaftar

🧩 It's puzzle time! Try our newest crossword: either!

🔗 - creaftar.web.app/play

#solve #fun #crosswords #mentalexercise #words #either

0 0 0 0

Creaftar

@creaftar.com

11 months ago

Creaftar invite photo

🕹️ Take a break and solve our latest crossword: either!

🔗 - creaftar.web.app/play

#play #solve #either

0 0 0 0

Pup and Bear Travels

@pupandbeartravels.bsky.social

11 months ago

Phantom Manor or Haunted Mansion?

#hauntedmansion #phantommanor #waltdisneyworld #disneylandparis #disney #disneypark #disneyrides #disneyattractions #either #both

0 0 0 0

洪民憙 (Hong Minhee)

@hongminhee.hackers.pub.ap.brid.gy

11 months ago

Revisiting Java's Checked Exceptions: An Underappreciated Type Safety Feature Despite their bad reputation in the Java community, checked exceptions provide superior type safety comparable to Rust's `Result<T, E>` or Haskell's `Either`—we've been dismissing one of Java's best features all along. ## Introduction Few features in Java have been as consistently criticized as checked exceptions. Modern Java libraries and frameworks often go to great lengths to avoid them. Newer JVM languages like Kotlin have abandoned them entirely. Many experienced Java developers consider them a design mistake. But what if this conventional wisdom is wrong? What if checked exceptions represent one of Java's most forward-thinking features? In this post, I'll argue that Java's checked exceptions were ahead of their time, offering many of the same type safety benefits that are now celebrated in languages like Rust and Haskell. Rather than abandoning this feature, we should consider how to improve it to work better with modern Java's features. ## Understanding Java's Exception Handling Model To set the stage, let's review how Java's exception system works: * **Unchecked exceptions** (subclasses of `RuntimeException` or `Error`): These don't need to be declared or caught. They typically represent programming errors (`NullPointerException`, `IndexOutOfBoundsException`) or unrecoverable conditions (`OutOfMemoryError`). * **Checked exceptions** (subclasses of `Exception` but not `RuntimeException`): These must either be caught with `try`/`catch` blocks or declared in the method signature with `throws`. They represent recoverable conditions that are outside the normal flow of execution (`IOException`, `SQLException`). Here's how this works in practice: // Checked exception - compiler forces you to handle or declare it public void readFile(String path) throws IOException { Files.readAllLines(Path.of(path)); } // Unchecked exception - no compiler enforcement public void processArray(int[] array) { int value = array[array.length + 1]; // May throw ArrayIndexOutOfBoundsException } ## The Type Safety Argument for Checked Exceptions At their core, checked exceptions are a way of encoding potential failure modes into the type system via method signatures. This makes certain failure cases part of the API contract, forcing client code to explicitly handle these cases. Consider this method signature: public byte[] readFileContents(String filePath) throws IOException The `throws IOException` clause tells us something critical: this method might fail in ways related to IO operations. The compiler ensures you can't simply ignore this fact. You must either: 1. Handle the exception with a try-catch block 2. Propagate it by declaring it in your own method signature This type-level representation of potential failures aligns perfectly with principles of modern type-safe programming. ### Automatic Propagation: A Hidden Advantage One often overlooked advantage of Java's checked exceptions is their automatic propagation. Once you declare a method as `throws IOException`, any exception that occurs is automatically propagated to the caller without additional syntax. Compare this with Rust, where you must use the `?` operator every time you call a function that returns a `Result`: // Rust requires explicit propagation with ? for each call fn read_and_process(path: &str) -> Result<(), std::io::Error> { let content = std::fs::read_to_string(path)?; process_content(&content)?; Ok(()) } // Java automatically propagates exceptions once declared void readAndProcess(String path) throws IOException { String content = Files.readString(Path.of(path)); processContent(content); // If this throws IOException, it's automatically propagated } In complex methods with many potential failure points, Java's approach leads to cleaner code by eliminating the need for repetitive error propagation markers. ## Modern Parallels: Result Types in Rust and Haskell The approach of encoding failure possibilities in the type system has been adopted by many modern languages, most notably Rust with its `Result<T, E>` type and Haskell with its `Either a b` type. In Rust: fn read_file_contents(file_path: &str) -> Result<Vec<u8>, std::io::Error> { std::fs::read(file_path) } When calling this function, you can't just ignore the potential for errors—you need to handle both the success case and the error case, often using the `?` operator or pattern matching. In Haskell: readFileContents :: FilePath -> IO (Either IOException ByteString) readFileContents path = try $ BS.readFile path Again, the caller must explicitly deal with both possible outcomes. This is fundamentally the same insight that motivated Java's checked exceptions: make failure handling explicit in the type system. ## Valid Criticisms of Checked Exceptions If checked exceptions are conceptually similar to these widely-praised error handling mechanisms, why have they fallen out of favor? There are several legitimate criticisms: ### 1. Excessive Boilerplate in the Call Chain The most common complaint is the boilerplate required when propagating exceptions up the call stack: void methodA() throws IOException { methodB(); } void methodB() throws IOException { methodC(); } void methodC() throws IOException { // Actual code that might throw IOException } Every method in the chain must declare the same exception, creating repetitive code. While automatic propagation works well within a method, the explicit declaration in method signatures creates overhead. ### 2. Poor Integration with Functional Programming Java 8 introduced lambdas and streams, but checked exceptions don't play well with them: // Won't compile because map doesn't expect functions that throw checked exceptions List<String> fileContents = filePaths.stream() .map(path -> Files.readString(Path.of(path))) // Throws IOException .collect(Collectors.toList()); This forces developers to use awkward workarounds: List<String> fileContents = filePaths.stream() .map(path -> { try { return Files.readString(Path.of(path)); } catch (IOException e) { throw new UncheckedIOException(e); // Wrap in an unchecked exception } }) .collect(Collectors.toList()); ### 3. Interface Evolution Problems Adding a checked exception to an existing method breaks all implementing classes and calling code. This makes evolving interfaces over time difficult, especially for widely-used libraries and frameworks. ### 4. Catch-and-Ignore Anti-Pattern The strictness of checked exceptions can lead to the worst possible outcome—developers simply catching and ignoring exceptions to make the compiler happy: try { // Code that might throw } catch (Exception e) { // Do nothing or just log } This is worse than having no exception checking at all because it provides a false sense of security. ## Improving Checked Exceptions Without Abandoning Them Rather than abandoning checked exceptions entirely, Java could enhance the existing system to address these legitimate concerns. Here are some potential improvements that preserve the type safety benefits while addressing the practical problems: ### 1. Allow lambdas to declare checked exceptions One of the biggest pain points with checked exceptions today is their incompatibility with functional interfaces. Consider how much cleaner this would be: // Current approach - forced to handle or wrap exceptions inline List<String> contents = filePaths.stream() .map(path -> { try { return Files.readString(Path.of(path)); } catch (IOException e) { throw new RuntimeException(e); } }) .collect(Collectors.toList()); // Potential future approach - lambdas can declare exceptions List<String> contents = filePaths.stream() .map((String path) throws IOException -> Files.readString(Path.of(path))) .collect(Collectors.toList()); This would require updating functional interfaces to support exception declarations: @FunctionalInterface public interface Function<T, R, E extends Exception> { R apply(T t) throws E; } ### 2. Generic exception types in throws clauses Another powerful enhancement would be allowing generic type parameters in `throws` clauses: public <E extends Exception> void processWithException(Supplier<Void, E> supplier) throws E { supplier.get(); } This would enable much more flexible composition of methods that work with different exception types, bringing some of the flexibility of Rust's `Result<T, E>` to Java's existing exception system. ### 3. Better support for exception handling in functional contexts Unlike Rust which requires the `?` operator for error propagation, Java already automatically propagates checked exceptions when declared in the method signature. What Java needs instead is better support for checked exceptions in functional contexts: // Current approach for handling exceptions in streams List<String> contents = filePaths.stream() .map(path -> { try { return Files.readString(Path.of(path)); } catch (IOException e) { throw new RuntimeException(e); // Lose type information } }) .collect(Collectors.toList()); // Hypothetical improved API List<String> contents = filePaths.stream() .mapThrowing(path -> Files.readString(Path.of(path))) // Preserves checked exception .onException(IOException.class, e -> logError(e)) .collect(Collectors.toList()); ### 4. Integration with `Optional<T>` and `Stream<T>` APIs The standard library could be enhanced to better support operations that might throw checked exceptions: // Hypothetical API Optional<String> content = Optional.ofThrowable(() -> Files.readString(Path.of("file.txt"))); content.ifPresentOrElse( this::processContent, exception -> log.error("Failed to read file", exception) ); ## Comparison with Other Languages' Approaches It's worth examining how other languages have addressed the error handling problem: ### Rust's `Result<T, E>` and `?` operator Rust's approach using `Result<T, E>` and the `?` operator shows how propagation can be made concise while keeping the type safety benefits. The `?` operator automatically unwraps a successful result or returns the error to the caller, making propagation more elegant. However, Rust's approach requires explicit propagation at each step, which can be more verbose than Java's automatic propagation in certain scenarios. ### Kotlin's Approach Kotlin made all exceptions unchecked but provides functional constructs like `runCatching` that bring back some type safety in a more modern way: val result = runCatching { Files.readString(Path.of("file.txt")) } result.fold( onSuccess = { content -> processContent(content) }, onFailure = { exception -> log.error("Failed to read file", exception) } ) This approach works well with Kotlin's functional programming paradigm but lacks compile-time enforcement. ### Scala's `Try[T]`, `Either[A, B]`, and Effect Systems Scala offers `Try[T]`, `Either[A, B]`, and various effect systems that encode errors in the type system while integrating well with functional programming: import scala.util.Try val fileContent: Try[String] = Try { Source.fromFile("file.txt").mkString } fileContent match { case Success(content) => processContent(content) case Failure(exception) => log.error("Failed to read file", exception) } This approach preserves type safety while fitting well with Scala's functional paradigm. ## Conclusion Java's checked exceptions were a pioneering attempt to bring type safety to error handling. While the implementation has shortcomings, the core concept aligns with modern type-safe approaches to error handling in languages like Rust and Haskell. Copying Rust's `Result<T, E>` might seem like the obvious solution, but it would represent a radical departure from Java's established paradigms. Instead, targeted enhancements to the existing checked exceptions system—like allowing lambdas to declare exceptions and supporting generic exception types—could preserve Java's unique approach while addressing its practical limitations. The beauty of such improvements is that they'd maintain backward compatibility while making checked exceptions work seamlessly with modern Java features like lambdas and streams. They would acknowledge that the core concept of checked exceptions was sound—the problem was in the implementation details and their interaction with newer language features. So rather than abandoning checked exceptions entirely, perhaps we should recognize them as a forward-thinking feature that was implemented before its time. As Java continues to evolve, we have an opportunity to refine this system rather than replace it. In the meantime, next time you're tempted to disparage checked exceptions, remember: they're not just an annoying Java quirk—they're an early attempt at the same type safety paradigm that newer languages now implement with much celebration. What do you think? Could these improvements make checked exceptions viable for modern Java development? Or is it too late to salvage this controversial feature? I'm interested in hearing your thoughts in the comments.

2 3 1 1

d

@diiii2.bsky.social

1 year ago

MELTING SYRUP BALM Either&は肌キメと毛穴をキレイに手軽くカバーするベースメイクを中心にビューティーノウハウを伝えるベーススペシャリストです。

ピリッとするけど、保湿力上げてくれるからいい感じ。前にDiorで似た製品があって、Diorのはもう少しリキッド寄りだったけど、こっちは固形。でも、その分1年ぐらいは保ちそう。
ピリッとするのが苦手な人は、アイシーブルーを選んだ方がいいのかも。
(今見たら、スパイシーピンクはソールドアウトしてて、アイシーブルーしか残ってなかった)

#dのコスメ記録
 #Either&
#Eitherand
#メルティングシロップバーム
 #スパイシーピンク
eitherand.jp/products/mel...

0 0 0 0

d

@diiii2.bsky.social

1 year ago

イーザーアンドの下地、リップバーム、コンシーラーと特典のエスパのジゼルのアクリルスタンド。

Either&のジゼルの特典つきコスメが届いたよう〜！アクスタ大事に飾ります…(結構でかいね…)
#Either&
#Eitherand
#dのコスメ記録
 #aespa
#æspa
#GISELLE

0 0 1 0

Laura Phillips

@lauraphillips.bsky.social

1 year ago

Bowen: Trump-Zelensky row signals looming crisis between Europe and US Doubts are growing about the US commitment to European security outside Ukraine.

BBC’s International Ed Jeremy Bowen: “There are suspicions now that the public row was - in the words of 1 diplomatic observer - a planned political mugging: #either to force #Zelensky to do America's bidding, or to precipitate a crisis that would allow them to blame him for whatever happens next”1/

16 6 5 0

Posts tagged #Either