Ready for some wordplay? Sharpen your skills with Slate’s puzzle for April 26, 2024.

Slate Crossword: Shooting Stars’ Org.? (Three Letters)

Welcome to Slate’s weekly news quiz. It’s Friday, which means it’s time to test your knowledge of the week’s news events. Your host, Ray Hamel, has concocted questions on news topics ranging from politics to business, from culture to sports to science.

Slate News Quiz: Trump trial, bird flu, campus protests.

Photo illustration by Slate. Images by carles miro/iStock/Getty Images Plus and Getty Images Plus.

Help! I Agreed to Be My Friend’s Maid of Honor, but Her Relationship Is a Giant Red Flag.

Photo illustration by Slate. Photo by Getty Images Plus.

Parenting advice: My kid has a very strange idea about how she’ll become “talented.”

Photo illustration by Slate. Photos by Alex Wong/Getty Images and Erin Schaff/Pool/Getty Images.

Supreme Court immunity arguments: The court just showed how and why it will let Donald Trump get away with it.

The threat of a “prohibition” in the United States, and that ByteDance could lose out on a lot of money, is merely the law’s way to force a sale of the propaganda dance app and put it in the hands of a patriotic American company, such as McDonald’s or Slate.

Will TikTok be banned in the U.S.? Explaining why Joe Biden signed the China-related law.

Test your wits on the Slate Quiz for April 25, 2024.

Trivia quiz: Slate’s daily game of questions about science.

Ready for some wordplay? Sharpen your skills with Slate’s puzzle for April 25, 2024.

Slate Crossword: Namesake of a Razor You Can’t Shave With (Five Letters)

When you&#x27;ve lost Justice Barrett on an abortion case ...

The Lawyer Defending Idaho’s Abortion Ban Irritated the One Justice He Needed on His Side

Photo illustration by Slate. Photo by MoreISO/Getty Images Plus and Jordan Pettitt/PA Images via Getty Images.

Five Escaped Horses Rampaged Through Central London for Two Hours This Morning, By the Way

OUR MISSION\nSlate has big ambitions: We were born out of our Founders’ own experiences to solve the problems we all faced with social media

Slate

Building an awesome editor for your React-based web application is by no means easy. But with things get much easier. Even with the help of Slate, building a full-featured editor is way more work than we can cover in one blog post, so this post will give you the big picture and subsequent posts will dive into the dirty details. SlateJS Note: this post is based on a recent talk at the JavaScript NYC meetup. You can watch the video here: SlateJS We're building , a new, fast, and highly collaborative alternative to issue trackers like Jira, Trello, and Clubhouse. We're big believers in remote work, and in particular working asynchronously so that team members get large, uninterrupted blocks of time to get work done. A key to supporting this type of work is having a really great editor so that teams are inspired to collaborate together on issues and ensure alignment. And we think we've got the best editor around: Kitemaker Markdown shortcuts, code blocks with syntax highlighting, images, embedding designs from , math expressions with LaTex, diagrams with , and, of course, emojis ♥️. All done entirely with Slate. Figma MermaidJS So why did we choose to go with Slate in the first place? It's definitely not the only editor framework out there. For us, the things that pushed us towards Slate were: It's un-opinionated about how your document is structured, and that gave us the flexibility we needed It doesn't force any built-in toolbars or any other visuals upon you It's built with React in mind and that makes a huge difference when rendering complex documents It lays the foundation for collaborative editing which is something we believe is important for Kitemaker We really like the philosophy behind it It has a thriving community, particularly on Slack How Slate represents documents One of the best parts of Slate is how it holds very few opinions about how documents are structured. It has only a few concepts: Editor - the top level container of your document Block level elements - the domain-specific "chunks" that make up your documents, like paragraphs, code blocks and lists. These are the things you can draw horizontal lines between in your document Inline elements - special elements that flow inline with the text of your document, like links Text nodes - these contain the actual text in the document Marks - annotations placed on the text, such as marking text as bold or italic Astute readers will notice that this is structured very similar to the DOM, and text, block and inlines in Slate behave very much like their counterparts in the DOM. Here's an annotated screenshot of a Slate editor to explain these concepts visually: Slate uses a very simple JSON format for representing documents, and the document above would look like this in Slate's representation: [
 { : , : [
 { : },
 { : , : , : [
 { : }
 ]
 },
 { : }
 ]
 },
 { : , : [
 { : },
 { : , : },
 { : },
 { : , : },
 { : }
 ]
 }
] "type" "paragraph" "children" "text" "Text with a link " "type" "link" "url" "https://kitemaker.co" "children" "text" "https://kitemaker.co" "text" " here" "type" "paragraph" "children" "text" "Text with " "text" "bold" "bold" true "text" " and " "text" "italic" "italic" true "text" " here" As we said before, Slate is really un-opinionated about how documents are structured. In the JSON blob above, the only thing Slate cares about is that it gets an array of block elements with a property and that those children are either other block elements, or a mixture of text nodes and inline elements. That's it. Slate doesn't care about the , or properties and it doesn't care about how these various nodes will be rendered. This makes it really flexible and powerful to work with. children type url bold Hello world editor Enough background. Let's look at some code! Let's see what a simple editor component looks like using Slate: { editor = useMemo( withReact(createEditor()), []); [value, setValue] = React.useState<Node[]>([
 { : [{ : }],
 },
 ]); ( <Editable /> );
} ( ) function MyEditor const => () const children text 'Testing' return setValue(v)}> < = = = => Slate editor {editor} value {value} onChange {(v) </ > Slate And that's it. That's an entire working component with Slate! We use to make ourselves an editor (don't worry about for now - that's a plugin, which we'll discuss below) createEditor() withReact() We make a simple array of nodes to store the document (just like we looked at above) We instantiate a component which serves as a context provider, providing the editor we created above to all of the components below it. This is really cool because you can, for example, add toolbars and other components below the component that can grab the editor and manipulate the document with it. We also wire up the and properties, similar to any input in React <Slate> <Slate> value onChange We add an component which is the actual editor the user interacts with on the screen <Editable> Boring. How do we extend things? So while that previous example was trivial to write, we still only have an editor that works about as well as . Not very exciting. <TextArea> Luckily Slate provides mechanisms for making things a whole lot more interesting: plugins allow us to override the core behavior of the editor. They're not concerned with rendering, just with overriding what happens when (for example) text is inserted, or an image is dropped Plugins: allow us to handle things like key presses, so we can add hotkeys or allow pressing 'tab' to indent a bulleted list Event handlers: with Slate we can specify exactly how each and every node in our document should be rendered using React Custom rendering with React: Let's take a quick look at each of these. Plugins Plugins are a deceptively simple, powerful concept in Slate. Plugins generally look something like this: { { insertText, insertData, normalizeNode, isVoid, isInline } = editor; editor.insertText = { insertText(text);
 }; editor.insertData = { insertData(data);
 }; editor.normalizeNode = { normalizeNode(entry);
 }; editor.isVoid = { (element.type === ) { ;
 } isVoid(element);
 }; editor.isInline = { (element.type === ) { ;
 } isInline(element);
 }; editor;
 } export ( ) function withMyPlugin editor: ReactEditor const // called whenever text is inserted into the document (e.g. when // the user types something) ( ) => text // do something interesting! // called when the users pastes or drags things into the editor ( ) => data // do something interesting! // we'll dedicate a whole post to this one, but the gist is that it's used // to enforce your own custom schema to the document JSON ( ) => entry // do something interesting! // tells slate that certain nodes don't have any text content (they're _void_) // super handy for stuff like images and diagrams ( ) => element if 'image' return true return // tells slate that certain nodes are inline and should flow with text, like // the link in our example above ( ) => element if 'link' return true return return By convention, their names start with . They take a Slate editor, override whatever functions they need to override and return the modified editor back. Very often, they handle a few cases in some of these functions and fall back to the default behavior for the rest. about 80% of adding functionality to a Slate editor is doing string matching in these plugin functions and then manipulate the document using Slate's rich API. with Spoiler alert: There are more functions you can override than the ones shown above, but these are the most common by far. You can read all about plugins in . Slate's documentation One of the most powerful parts of Slate plugins is that they can be composed together. Each plugin can look for the things it cares about and pass everything else along unmodified. Then you can compose multiple plugins together and get an even more powerful editor: { editor = useMemo( withReact(withDragAndDrop(withMarkdownShortcuts(withEmojis(withReact(createEditor())))), []);
 ...
} ( ) function MyEditor const => () Event handlers Like many React input components, the component has a bunch of events to which you can listen. We don't have time to go through them all here, but we'll mention the one we use most often: <Editable> onKeyDown() By handling this event, we can do all sorts of powerful things in our editor, like adding hotkeys for example: <Editable
 onKeyDown={(e) => { (e.metaKey && e.key === ) {
 e.preventDefault();
 Editor.addMark(editor, , );
 }
 }}
 ...
/> // let's make the current text bold if the user holds command and hits "b" if 'b' 'bold' true We use key down events in Kitemaker: everywhere Nesting and un-nesting lists when tab is pressed Breaking out of lists and code blocks when enter (or in some cases backspace) is pressed Splitting blocks (e.g. headlines) when enter is pressed in the middle of a block And many many more Custom rendering with React Slate has no opinions on how your blocks and inlines should look on the screen. By default, it just shoves all blocks into plain elements and all inlines into plain elements, but that's pretty dull. <div> To override Slate's default behavior, all we need to do is pass a function into the component's property: <Editable> renderElement <Editable
 renderElement={({ element, attributes, children }) => { (element.type) { : ; : ; : ;
 }
 }}
/> switch case 'code' return {children} < { }> pre ...attributes </ > pre case 'link' return {children} < = { }> a href {element.url} ...attributes </ > a default return {children} < { }> div ...attributes </ > div All this code is doing is looking for the property on a node and picking a different rendering path based on that. Remember, as we said before, Slate doesn't care about these properties, only do. So while the convention is to use to denote the type of a node, nothing is forcing you to do so. You can also add all sorts of other properties to your components that help with the rendering (like the url property we saw on links above). type we type The things returned from just need to be React components. What they look like and their complexity is entirely up to you. Here we're returning a simple element to denote a code block, but nothing is stopping us from returning a full blown component that supports syntax highlighting (like we do in Kitemaker). renderElement <pre> <Code> There's only one important thing to remember when implementing your own rendering - always spread the parameter as properties on the topmost component you're returning. If you don't, Slate won't be able to do its own internal bookkeeping and things will go very badly for you. attributes This has been a super quick introduction to custom rendering, so don't worry if you don't fully grasp it yet. What's tricky in Slate? You've now seen some of the basics of Slate, so you're ready to start experimenting. We thought we'd warn you a little about some of the pitfalls and tricky parts of working with Slate so you'll see them coming and not get discouraged: copying and pasting on the web is a mess. We'll dedicate a whole post to how we handle this in Kitemaker. Short version is that to test our own "paste logic", we have made a somewhat complex document in a bunch of popular web editors Google docs, Notion, Dropbox Paper, Quip, etc. Copying and pasting: by default, Slate doesn't support undo/redo. It does however come with a plugin called that provides this functionality. However, we've found that this doesn't provide the exact user experience we're looking for and so we've had to extend it ourselves History: useHistory() dealing with things that pop up and need to be positioned correctly (like what you see in the Kitemaker editor above when "/" is typed to insert a block or "@" is typed to mention a user) can be pretty tricky Hovers/floating menus: Kitemaker is a product with a ton of hotkeys for everything (we want our users to be able to use it without lifting their hands off the keys) but sometimes there have been some challenges with the key handling in Slate "fighting" with our hotkeys Key handling: Slate's API is quite extensive and we haven't even begun to touch on it in this post. There are many, many functions for manipulating the document (adding nodes, removing nodes, splitting nodes, wrapping nodes, adding text, deleting words, etc.) and it's not always totally obvious which API to use in which situation Big API surface: we've had complaints from users using MBPs and also things like pen inputs for writing Japanese. There's a to fix some strange behaviors so hopefully it'll be fixed soon 🤞 Some wonkiness with input methods like the Macbook Pro touch bar: PR open We'll cover some of these advanced topics in our subsequent posts. And a brief word of warning While we've been very happy with Slate so far, there are a few warnings that any team embarking on building their own editor should be aware of: Like any open source project, progress on Slate comes in waves. While there was a huge rewrite last year and things moved really quickly, progress has now slowed down considerably. There are lots of open issues and open PRs. We hope we can do our share to improve this going forward, but the community could use more support After the rewrite last year, the documentation hasn't quite gotten back to the standard it was before the rewrite. There's a fair amount of stubbed-out documentation that lacks the details required by developers who are just getting started with the project. We've submitted some changes to improve this, but more work is needed Slate is not properly supported on Android. Fortunately, there was a to fix this. Awesome! 🤙 Kickstarter project funded More to come! We hope this served as a nice high level introduction to Slate for you and gave you some of the information you need about whether or not to give Slate a try. There is way way way too much material to cover in a single post, but there will be a number of posts that follow that dig into some of the more complex topics. Thanks for reading! Did you find this article useful? If you want to see more material like this follow and on Twitter. @ksimons @KitemakerHQ Kevin Simons is the CTO of Kitemaker, the super-fast issue tracker that gives distributed teams superpowers Previously published at https://blog.kitemaker.co/building-a-rich-text-editor-in-react-with-slatejs

How We Built A Rich Text Editor in React with SlateJS

Last week . Google has promoted Chromebook devices as productivity machines for years but up until announcing at the 2018 Android Developer Summit this was not the case for Android developers like myself. When I started coding in 2014 I looked forward to being able to write and use the same apps across my phone and computer via a powerful and portable Chromebook. The Pixel Slate is that Chrome Os device. Pixel Slate started shipping to customers support for Android Studio Pixel Slate Is Great For Android and Web Developers With the balance of software flexibility, power, and design, if I knew I was solely developing for Android and backend moving forward I would make the leap from my current Macbook Pro to the . Pixel Slate What’s Enticing About Pixel Slate For Developers via native Linux support. Run almost any development software are becoming more common with high end Chromebooks such as the , , and leading the charge. Although Pixel Slate is not in the same league as a fully decked out Macbook Pro, the Slate seems to have plenty of fire power for compiling and running apps. As context, according to the processor benchmark scores from below, Pixel Slate has almost the power of my 2009 13’’ Macbook Pro which I’m still developing Android apps without issue. Powerful processors enough Pixel Slate Pixelbook Acer Chromebook Spin 13 Geekbench 4 3x 10 year old Processor Scores Geekbench 4 potentially compared to using an emulator. Test Android apps directly on the device without using a physical device. Test real-world usage with touchscreen without taking up a whole table. No one should want to be the shmuck in a cafe using an entire table with a laptop stand and bluetooth keyboard. Elevating the screen is great because it puts less strain on the neck. how staring down puts additional weight on the neck and spine which is not healthy. With the Pixel Slate tablet form factor elevating only the screen uses half the space as a traditional laptop. With a laptop there are 2 keyboards worth of space, the keyboard attached to the laptop and a separate keyboard for typing. Brydge, a popular keyboard for iPads, makes a which is better than the because it offers a firm hinge when connected. Save your neck The Atlantic highlights Pixel Slate keyboard Google keyboard The Atlantic, What Texting Does to the Spine by OLGA KHAZAN For All Users that is not possible with web apps. More functionality with Android apps Naming a few features: and : View inboxes for all accounts at once. Gmail Google Calendar : No standalone web app. Google Tasks : Messaging. Instagram : Listen to converted text to audio content. Pocket , , : Offline content. Pocket Casts YouTube Netflix with the by Google seems like a great solution for those who love to take hand written notes on the go. Note taking pressure sensitive pen for unlocking the device and potentially passwords and payments. Fingerprint sensor with a . Charge on the go USB-C battery pack , thanks again to USB-C. Fast charge other devices Wirecutter: The Best USB-C Battery Packs and Power Banks Why I’m Not Buying One Max Storage Option is Low Considering similar device’s specs and the fact that the fully spec’d Pixel Slate is I’d hope to have 500 GB. Last year’s Pixelbook offers 500 GBs and the new iPad pro offer a 1 TB option. This is not a deal breaker. $1,599 I could still make the max 250 GB Pixel Slate work. With my estimate based on current phone and Macbook usage I’d use 146 GB leaving me at 58% capacity. A lack of storage can cause performance issues so to start off at 58% capacity is workable, but not ideal if you’re aiming to the device for years to come. according to CNet Minimum estimated required storage needed for computer. ’Hacky’ Solutions for iOS Development I view purchasing tech as a long term investment. As I said above, I’m still using my 2009 Macbook Pro with many components updated. Currently I’m writing Android apps which would be great with the Pixel Slate. However, if there is any possibility of getting into iOS development in the future there is no way to do so cleanly on a Chrome Os device. . This is a deal breaker. Xcode is restricted to macOs only The options for iOS development on a Chromebook are: Running macOs off a virtual machine thus breaking Apple’s End User License Agreement. Using a cloud solution such as which even if it doesn’t have performance issues, if you use a cross platform solution such as or you’ll have to do that all in the cloud environment to run both Android and iOS at the same time. macInCloud Flutter ReactNative Therefore I must bend the knee to Apple. prettywhiskey.com Potential iOS Development Solutions (not likely in the short term) Either Google’s Flutter or Facebook’s ReactNative creates a process to submit iOS apps without requiring Xcode on your local machine. King Cook opens up Xcode for non macOs devices. I’m Adam Hurwitz — hit the clapping hands icon and check out the rest of my writing if you enjoyed the above. Thanks for reading!

Pixel Slate is (Almost) Great For Developers

Singularity: Streamlining Game Development with a Universal Backend Framework

এককতা: একটি ইউনিভার্সাল ব্যাকএন্ড ফ্রেমওয়ার্ক সহ গেম ডেভেলপমেন্টকে স্ট্রীমলাইন করা

Singularity: Optimierte Spieleentwicklung mit einem universellen Backend-Framework

Singularidad: agilización del desarrollo de juegos con un marco de backend universal

Singularity : rationaliser le développement de jeux avec un framework backend universel

सिंगलेरिटी: यूनिवर्सल बैकएंड फ्रेमवर्क के साथ गेम डेवलपमेंट को सुव्यवस्थित करना

Singularity: ユニバーサル バックエンド フレームワークによるゲーム開発の効率化

Singularity: 범용 백엔드 프레임워크로 게임 개발 간소화

Singularidade: simplificando o desenvolvimento de jogos com uma estrutura de back-end universal

Singularity: оптимизация разработки игр с помощью универсальной серверной платформы

Tekillik: Evrensel Arka Uç Çerçevesiyle Oyun Geliştirmeyi Kolaylaştırma

Điểm kỳ dị: Hợp lý hóa quá trình phát triển trò chơi với Khung phụ trợ phổ quát

Singularity：使用通用后端框架简化游戏开发

By Amanda Kavanagh While tech sectors like healthcare, climate tech and cybersecurity are urgently focused on retraining in AI, it’s not quite as important for other programmers. That’s according to Christian Rebernik, co-chief executive and co-founder of Tomorrow University of Applied Sciences, who reckons you don’t need to throw the baby out of the bath water, and ditch your expertise for AI. In an interview with the Financial Times, he makes this recommendation: “You can secure yourself, if you are a top-tier expert who can help teach AI in your field . . . [you can] earn from training models on data set created by you.” 3 high-paying roles to apply for today DevOps Engineer, Accenture Federal Services, Chantilly ($76,000 - $144,000)
Principal DevOps Engineer, Autodesk, TX ($141,400 - $228,800)
Staff/Sr. Staff DevOps Engineer, SciTec, Boulder ($93,000 - $137,000) The key is deep knowledge. As subject matter expertise really matters when it comes to creating the best prompts, once you’ve an understanding of prompt engineering, and experiment with AI tools in your day-to-day life, that may be enough for now. This frees programmers up to focus on the languages making waves in the coding community; here we’ll look at three of the newest and well-paid languages of the moment. Zig Created by Andrew Kelley in 2015, Zig is pitched as a general purpose language and as a modern alternative to C, but it’s still relatively obscure. In a Stack Overflow survey of 89,184 software developers across 185 countries, just 0.83% reported proficiency in Zig. However, the same survey also found that Zig developers command the highest median salaries on average. Median earnings of $103,000 may be pocket change to some in highly-paid AI roles, and it won’t put you in the top 10% of earners in the U.S. – you’ll need to be on $167,639 for that – but it’s the only programming language that hits six figures in the Stack Overflow survey. The next closest is Erlang ($99,492), F# ($99,492), Ruby ($98,522), and in fourth place, the former 2022 leader, Clojure ($96,381). Comparatively, the bottom four are: Visual Basic (.Net) with $65,000 median pay, MATLAB with $61,735, PHP at $58,899, and Dart, which commands the least at $55,862. Because Zig is compatible with C codebases, it may be readily incorporated with current projects, making it a solid option for systems development, embedded systems, game design, and scripting. Non-profit Zig boasts a vibrant contributor community where developers are invited to utilize it for personal open-source projects, allowing real-world problems to surface and be resolved in real-time. Its rarity makes it something of a risk, as you may have to plug and play, figuring out mistakes as you go. Depending on the pace in your current role, this may or may not be possible. But clearly, there can be salary gains if you can find a company that utilizes and values Zig. Finch Finch is the latest programming language from MIT, which was announced earlier this year. It aims to resolve the challenges associated with computing over-structured arrays. Finch does this by providing a programming model that unifies control flow and diverse data structures into a single representation that allows for co-optimization. Specifically, it automates the control flow to the data, freeing up performance engineers to experiment with many algorithms. MIT says that Finch is, to the best of its knowledge, the first programming language to support affine indexing or scatter/gather of sparse or structured operands, as well as if-conditions, early breaks, and multiple left hand sides over structured data. Early-adopters are praising the time-saving automatic specialization and smooth control flow, particularly in fields like image processing and scientific computing, where structured data is essential. Being a complete newbie, Finch doesn’t have a vast library of tools and frameworks to refer to, meaning it’s not really suitable for large-scale projects just yet. But if you’re a keen early-adopter, Finch is one to watch, and as the community expands, it may become a very valuable tool in the near future. Swift Apple’s Swift has been knocking around for a decade, but its next iteration – Swift 6 – is slated for release later this year. This is the first major update since Swift 5, five long years ago. This release expands upon the async/await, existentials, and macros capabilities that were first included in the Swift 5.x series. Apple director of languages and runtimes, Ted Kremenek says, “Swift’s safety, speed, and approachability, combined with built-in C and C++ interoperability, mean Swift is the best choice to succeed C++.” Meanwhile, forums and blogs are already advising programmers on how to migrate projects across, which is expected to be tricky for legacy codebases. 3 great tech jobs hiring now DevOps Engineer - Sports Technology, Electronic Arts, Orlando
Sr. DevOps Engineer - Store Frontend, hims & hers, San Francisco ($155,000 - $175,000)
Senior Engineer Fullstack (Java), GTT LLC, Chevy Chase The good news is there is clear demand for Swift programmers. According to jobs site Indeed, iOS developers and senior mobile developers are sought after in major companies all over the world, including Accenture, DataAnnotation, and Netflix. It’s widely-accepted that for a long, productive, and well-paid career in programming, developers must always move with the times. Ideally, your existing role will allow time for experimentation and upskilling, enabling you to explore these languages and integrate them into your projects. But if upskilling isn’t a priority in your workplace, it could be time to look for something new. Ready to find your next role in tech? Whether you want to pivot to AI or put your coding expertise to good use, visit the Hackernoon Job Board today By Amanda Kavanagh While tech sectors like healthcare, climate tech and cybersecurity are urgently focused on retraining in AI, it’s not quite as important for other programmers. That’s according to Christian Rebernik, co-chief executive and co-founder of Tomorrow University of Applied Sciences, who reckons you don’t need to throw the baby out of the bath water, and ditch your expertise for AI. In an interview with the Financial Times , he makes this recommendation: “You can secure yourself, if you are a top-tier expert who can help teach AI in your field . . . [you can] earn from training models on data set created by you.” Financial Times Financial Times 3 high-paying roles to apply for today 3 high-paying roles to apply for today DevOps Engineer, Accenture Federal Services, Chantilly ($76,000 - $144,000) Principal DevOps Engineer, Autodesk, TX ($141,400 - $228,800) Staff/Sr. Staff DevOps Engineer, SciTec, Boulder ($93,000 - $137,000) DevOps Engineer, Accenture Federal Services, Chantilly ($76,000 - $144,000) DevOps Engineer, Accenture Federal Services, Chantilly ($76,000 - $144,000) DevOps Engineer, Accenture Federal Services, Chantilly ($76,000 - $144,000) Principal DevOps Engineer, Autodesk, TX ($141,400 - $228,800) Principal DevOps Engineer, Autodesk, TX ($141,400 - $228,800) Principal DevOps Engineer, Autodesk, TX ($141,400 - $228,800) Staff/Sr. Staff DevOps Engineer, SciTec, Boulder ($93,000 - $137,000) Staff/Sr. Staff DevOps Engineer, SciTec, Boulder ($93,000 - $137,000) Staff/Sr. Staff DevOps Engineer, SciTec, Boulder ($93,000 - $137,000) The key is deep knowledge. As subject matter expertise really matters when it comes to creating the best prompts, once you’ve an understanding of prompt engineering, and experiment with AI tools in your day-to-day life, that may be enough for now. This frees programmers up to focus on the languages making waves in the coding community; here we’ll look at three of the newest and well-paid languages of the moment. Zig Zig Created by Andrew Kelley in 2015, Zig is pitched as a general purpose language and as a modern alternative to C, but it’s still relatively obscure. In a Stack Overflow survey of 89,184 software developers across 185 countries, just 0.83% reported proficiency in Zig. Stack Overflow survey Stack Overflow survey However, the same survey also found that Zig developers command the highest median salaries on average. Median earnings of $103,000 may be pocket change to some in highly-paid AI roles , and it won’t put you in the top 10% of earners in the U.S. – you’ll need to be on $167,639 for that – but it’s the only programming language that hits six figures in the Stack Overflow survey. highly-paid AI roles highly-paid AI roles The next closest is Erlang ($99,492), F# ($99,492), Ruby ($98,522), and in fourth place, the former 2022 leader, Clojure ($96,381). Comparatively, the bottom four are: Visual Basic (.Net) with $65,000 median pay, MATLAB with $61,735, PHP at $58,899, and Dart, which commands the least at $55,862. Because Zig is compatible with C codebases, it may be readily incorporated with current projects, making it a solid option for systems development, embedded systems, game design, and scripting. Non-profit Zig boasts a vibrant contributor community where developers are invited to utilize it for personal open-source projects, allowing real-world problems to surface and be resolved in real-time. vibrant contributor community vibrant contributor community Its rarity makes it something of a risk, as you may have to plug and play, figuring out mistakes as you go. Depending on the pace in your current role, this may or may not be possible. But clearly, there can be salary gains if you can find a company that utilizes and values Zig. company company Finch Finch Finch is the latest programming language from MIT, which was announced earlier this year. It aims to resolve the challenges associated with computing over-structured arrays. Finch Finch Finch does this by providing a programming model that unifies control flow and diverse data structures into a single representation that allows for co-optimization. Specifically, it automates the control flow to the data, freeing up performance engineers to experiment with many algorithms. MIT says that Finch is, to the best of its knowledge, the first programming language to support affine indexing or scatter/gather of sparse or structured operands, as well as if-conditions, early breaks, and multiple left hand sides over structured data. Early-adopters are praising the time-saving automatic specialization and smooth control flow, particularly in fields like image processing and scientific computing, where structured data is essential. Being a complete newbie, Finch doesn’t have a vast library of tools and frameworks to refer to, meaning it’s not really suitable for large-scale projects just yet. But if you’re a keen early-adopter, Finch is one to watch, and as the community expands, it may become a very valuable tool in the near future. Swift Apple’s Swift has been knocking around for a decade, but its next iteration – Swift 6 – is slated for release later this year. This is the first major update since Swift 5, five long years ago. This release expands upon the async/await, existentials, and macros capabilities that were first included in the Swift 5.x series. Apple director of languages and runtimes, Ted Kremenek says, “Swift’s safety, speed, and approachability, combined with built-in C and C++ interoperability, mean Swift is the best choice to succeed C++.” Meanwhile, forums and blogs are already advising programmers on how to migrate projects across, which is expected to be tricky for legacy codebases. 3 great tech jobs hiring now DevOps Engineer - Sports Technology, Electronic Arts, Orlando Sr. DevOps Engineer - Store Frontend, hims & hers, San Francisco ($155,000 - $175,000) Senior Engineer Fullstack (Java), GTT LLC, Chevy Chase DevOps Engineer - Sports Technology, Electronic Arts, Orlando DevOps Engineer - Sports Technology, Electronic Arts, Orlando DevOps Engineer - Sports Technology, Electronic Arts, Orlando Sr. DevOps Engineer - Store Frontend, hims & hers, San Francisco ($155,000 - $175,000) Sr. DevOps Engineer - Store Frontend, hims & hers, San Francisco ($155,000 - $175,000) Sr. DevOps Engineer - Store Frontend, hims & hers, San Francisco ($155,000 - $175,000) Senior Engineer Fullstack (Java), GTT LLC, Chevy Chase Senior Engineer Fullstack (Java), GTT LLC, Chevy Chase Senior Engineer Fullstack (Java), GTT LLC, Chevy Chase The good news is there is clear demand for Swift programmers. According to jobs site Indeed, iOS developers and senior mobile developers are sought after in major companies all over the world, including Accenture, DataAnnotation, and Netflix. It’s widely-accepted that for a long, productive, and well-paid career in programming, developers must always move with the times. Ideally, your existing role will allow time for experimentation and upskilling, enabling you to explore these languages and integrate them into your projects. But if upskilling isn’t a priority in your workplace, it could be time to look for something new. Ready to find your next role in tech? Whether you want to pivot to AI or put your coding expertise to good use, visit the Hackernoon Job Board today Ready to find your next role in tech? Whether you want to pivot to AI or put your coding expertise to good use, visit the Hackernoon Job Board today Ready to find your next role in tech? Whether you want to pivot to AI or put your coding expertise to good use, visit the Hackernoon Job Board today Ready to find your next role in tech? Whether you want to pivot to AI or put your coding expertise to good use, visit the Hackernoon Job Board today Ready to find your next role in tech? Whether you want to pivot to AI or put your coding expertise to good use, visit the Hackernoon Job Board today

3 High Paying Programming Languages Jobs On Developers’ Watchlists

ডেভেলপারদের ওয়াচলিস্টে 3টি উচ্চ অর্থপ্রদানকারী প্রোগ্রামিং ভাষার চাকরি

3 gut bezahlte Jobs im Bereich Programmiersprachen auf den Beobachtungslisten der Entwickler

3 trabajos de lenguajes de programación bien remunerados en las listas de vigilancia de desarrolladores

3 emplois bien rémunérés dans les langages de programmation sur les listes de surveillance des développeurs

डेवलपर्स की वॉचलिस्ट पर 3 उच्च भुगतान वाली प्रोग्रामिंग भाषा नौकरियां

開発者の注目リストに載っている高収入のプログラミング言語の仕事 3 つ

개발자 관심 목록에 있는 고임금 프로그래밍 언어 직업 3가지

3 empregos em linguagens de programação com altos salários nas listas de observação dos desenvolvedores

3 высокооплачиваемые вакансии в области языков программирования в списках разработчиков

Geliştiricilerin İzleme Listelerindeki Yüksek Ücretli 3 Programlama Dili İşi

3 công việc về ngôn ngữ lập trình được trả lương cao trong danh sách theo dõi của các nhà phát triển

开发人员关注的 3 个高薪编程语言职位

How Trump v United States Will Affect the Country Moving Forward

Trump v. United States Court Filing, retrieved on July 1, 2024, is part of HackerNoon’s Legal PDF Series. You can jump to any part in this filing here. This part is 17 of 21. VII Today’s decision to grant former Presidents immunity for their official acts is deeply wrong. As troubling as this criminal immunity doctrine is in theory, the majority’s application of the doctrine to the indictment in this case is perhaps even more troubling. In the hands of the majority, this new official-acts immunity operates as a one-way ratchet. First, the majority declares all of the conduct involving the Justice Department and the Vice President to be official conduct, see ante, at 19–24, yet it refuses to designate any course of conduct alleged in the indictment as private, despite concessions from Trump’s counsel.[6] Trump’s counsel conceded, for example, that the allegation that Trump “turned to a private attorney who was willing to spread knowingly false claims of election fraud to spearhead his challenges to the election results” “sounds private.” Tr. of Oral Arg. 29. He likewise conceded that the allegation that Trump “conspired with another private attorney who caused the filing in court of a verification signed by [Trump] that contained false allegations to support a challenge” “sounds private.” Ibid.; see also id., at 36–37 (Trump’s counsel explaining that it is not “disputed” that such conduct is “unofficial”). Again, when asked about allegations that “[t]hree private actors . . . helped implement a plan to submit fraudulent slates of presidential electors to obstruct the certification proceeding, and [Trump] and a co-conspirator attorney directed that effort,” Trump’s counsel conceded the alleged conduct was “private.” Id., at 29–30. Only the majority thinks that organizing fraudulent slates of electors might qualify as an official act of the President, see ante, at 24–28, or at least an act so “interrelated” with other allegedly official acts that it might warrant protection, ante, at 28. If the majority’s sweeping conception of “official acts” has any real limits, the majority is unwilling to reveal them in today’s decision. Second, the majority designates certain conduct immune while refusing to recognize anything as prosecutable. It shields large swaths of conduct involving the Justice Department with immunity, see ante, at 19–21; see also Part V, supra, but it does not give an inch in the other direction. The majority admits that the Vice President’s responsibility “‘presiding over the Senate’” is “‘not an “executive branch” function,’” and it further admits that the President “plays no direct constitutional or statutory role” in the counting of electoral votes. Ante, at 23–24. Yet the majority refuses to conclude that Trump lacks immunity for his alleged attempts to “enlist the Vice President to use his ceremonial role at the January 6 certification proceeding to fraudulently alter the election results.” App. 187, Indictment ¶10(d). Instead, it worries that a prosecution for this conduct might make it harder for the President to use the Vice President “to advance [his] agenda in Congress.” Ante, at 24. Such a prosecution, according to the majority, “may well hinder the President’s ability to perform his constitutional functions.” Ibid. Whether a prosecution for this conduct warrants immunity should have been an easy question, but the majority turns it into a debatable one. Remarkably, the majority goes further and declines to deny immunity even for the allegations that Trump organized fraudulent elector slates, pressured States to subvert the legitimate election results, and exploited violence at the Capitol to influence the certification proceedings. It is not conceivable that a prosecution for these alleged efforts to overturn a Presidential election, whether labeled official or unofficial under the majority’s test, would pose any “‘dangers of intrusion on the authority and functions of the Executive Branch,’” ante, at 14, and the majority could have said as much. Instead, it perseverates on a threshold question that should be immaterial. Looking beyond the fate of this particular prosecution, the long-term consequences of today’s decision are stark. The Court effectively creates a law-free zone around the President, upsetting the status quo that has existed since the Founding. This new official-acts immunity now “lies about like a loaded weapon” for any President that wishes to place his own interests, his own political survival, or his own financial gain, above the interests of the Nation. Korematsu v. United States, 323 U. S. 214, 246 (1944) (Jackson, J., dissenting). The President of the United States is the most powerful person in the country, and possibly the world. When he uses his official powers in any way, under the majority’s reasoning, he now will be insulated from criminal prosecution. Orders the Navy’s Seal Team 6 to assassinate a political rival? Immune. Organizes a military coup to hold onto power? Immune. Takes a bribe in exchange for a pardon? Immune. Immune, immune, immune. Let the President violate the law, let him exploit the trappings of his office for personal gain, let him use his official power for evil ends. Because if he knew that he may one day face liability for breaking the law, he might not be as bold and fearless as we would like him to be. That is the majority’s message today. Even if these nightmare scenarios never play out, and I pray they never do, the damage has been done. The relationship between the President and the people he serves has shifted irrevocably. In every use of official power, the President is now a king above the law. * * * The majority’s single-minded fixation on the President’s need for boldness and dispatch ignores the countervailing need for accountability and restraint. The Framers were not so single-minded. In the Federalist Papers, after “endeavor[ing] to show” that the Executive designed by the Constitution “combines . . . all the requisites to energy,” Alexander Hamilton asked a separate, equally important question: “Does it also combine the requisites to safety, in a republican sense, a due dependence on the people, a due responsibility?” The Federalist No. 77, p. 507 (J. Harvard Library ed. 2009). The answer then was yes, based in part upon the President’s vulnerability to “prosecution in the common course of law.” Ibid. The answer after today is no. Never in the history of our Republic has a President had reason to believe that he would be immune from criminal prosecution if he used the trappings of his office to violate the criminal law. Moving forward, however, all former Presidents will be cloaked in such immunity. If the occupant of that office misuses official power for personal gain, the criminal law that the rest of us must abide will not provide a backstop. With fear for our democracy, I dissent. Continue Reading Here. About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings.
This court case retrieved on July 1, 2024, supremecourt.gov is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction. [6] The majority protests that it is “adher[ing] to time-tested practices” by “deciding what is required to dispose of this case and remanding” to lower courts to sort out the details. Ante, at 41. Yet it implicitly acknowledges that it reaches far beyond what any lower court considered or any party briefed by designating certain conduct official in the first instance. See ibid. (noting “the lack of factual analysis in the lower courts, and the lack of briefing on how to categorize the conduct alleged”). In reaching out to shield some conduct as official while refusing to recognize any conduct as unofficial, the majority engages in judicial activism, not judicial restraint. Trump v. United States Court Filing, retrieved on July 1, 2024, is part of HackerNoon’s Legal PDF Series. You can jump to any part in this filing here. This part is 17 of 21. Trump v. United States Court Filing, retrieved on July 1, 2024, is part of HackerNoon’s Legal PDF Series . You can jump to any part in this filing here . This part is 17 of 21. HackerNoon’s Legal PDF Series here VII Today’s decision to grant former Presidents immunity for their official acts is deeply wrong. As troubling as this criminal immunity doctrine is in theory, the majority’s application of the doctrine to the indictment in this case is perhaps even more troubling. In the hands of the majority, this new official-acts immunity operates as a one-way ratchet. First, the majority declares all of the conduct involving the Justice Department and the Vice President to be official conduct, see ante, at 19–24, yet it refuses to designate any course of conduct alleged in the indictment as private, despite concessions from Trump’s counsel.[6] Trump’s counsel conceded, for example, that the allegation that Trump “turned to a private attorney who was willing to spread knowingly false claims of election fraud to spearhead his challenges to the election results” “sounds private.” Tr. of Oral Arg. 29. He likewise conceded that the allegation that Trump “conspired with another private attorney who caused the filing in court of a verification signed by [Trump] that contained false allegations to support a challenge” “sounds private.” Ibid.; see also id., at 36–37 (Trump’s counsel explaining that it is not “disputed” that such conduct is “unofficial”). Again, when asked about allegations that “[t]hree private actors . . . helped implement a plan to submit fraudulent slates of presidential electors to obstruct the certification proceeding, and [Trump] and a co-conspirator attorney directed that effort,” Trump’s counsel conceded the alleged conduct was “private.” Id., at 29–30. Only the majority thinks that organizing fraudulent slates of electors might qualify as an official act of the President, see ante, at 24–28, or at least an act so “interrelated” with other allegedly official acts that it might warrant protection, ante, at 28. If the majority’s sweeping conception of “official acts” has any real limits, the majority is unwilling to reveal them in today’s decision. Second, the majority designates certain conduct immune while refusing to recognize anything as prosecutable. It shields large swaths of conduct involving the Justice Department with immunity, see ante, at 19–21; see also Part V, supra, but it does not give an inch in the other direction. The majority admits that the Vice President’s responsibility “‘presiding over the Senate’” is “‘not an “executive branch” function,’” and it further admits that the President “plays no direct constitutional or statutory role” in the counting of electoral votes. Ante, at 23–24. Yet the majority refuses to conclude that Trump lacks immunity for his alleged attempts to “enlist the Vice President to use his ceremonial role at the January 6 certification proceeding to fraudulently alter the election results.” App. 187, Indictment ¶10(d). Instead, it worries that a prosecution for this conduct might make it harder for the President to use the Vice President “to advance [his] agenda in Congress.” Ante, at 24. Such a prosecution, according to the majority, “may well hinder the President’s ability to perform his constitutional functions.” Ibid. Whether a prosecution for this conduct warrants immunity should have been an easy question, but the majority turns it into a debatable one. Remarkably, the majority goes further and declines to deny immunity even for the allegations that Trump organized fraudulent elector slates, pressured States to subvert the legitimate election results, and exploited violence at the Capitol to influence the certification proceedings. It is not conceivable that a prosecution for these alleged efforts to overturn a Presidential election, whether labeled official or unofficial under the majority’s test, would pose any “‘dangers of intrusion on the authority and functions of the Executive Branch,’” ante, at 14, and the majority could have said as much. Instead, it perseverates on a threshold question that should be immaterial. Looking beyond the fate of this particular prosecution, the long-term consequences of today’s decision are stark. The Court effectively creates a law-free zone around the President, upsetting the status quo that has existed since the Founding. This new official-acts immunity now “lies about like a loaded weapon” for any President that wishes to place his own interests, his own political survival, or his own financial gain, above the interests of the Nation. Korematsu v. United States, 323 U. S. 214, 246 (1944) (Jackson, J., dissenting). The President of the United States is the most powerful person in the country, and possibly the world. When he uses his official powers in any way, under the majority’s reasoning, he now will be insulated from criminal prosecution. Orders the Navy’s Seal Team 6 to assassinate a political rival? Immune. Organizes a military coup to hold onto power? Immune. Takes a bribe in exchange for a pardon? Immune. Immune, immune, immune. Let the President violate the law, let him exploit the trappings of his office for personal gain, let him use his official power for evil ends. Because if he knew that he may one day face liability for breaking the law, he might not be as bold and fearless as we would like him to be. That is the majority’s message today. Even if these nightmare scenarios never play out, and I pray they never do, the damage has been done. The relationship between the President and the people he serves has shifted irrevocably. In every use of official power, the President is now a king above the law. * * * The majority’s single-minded fixation on the President’s need for boldness and dispatch ignores the countervailing need for accountability and restraint. The Framers were not so single-minded. In the Federalist Papers, after “endeavor[ing] to show” that the Executive designed by the Constitution “combines . . . all the requisites to energy,” Alexander Hamilton asked a separate, equally important question: “Does it also combine the requisites to safety, in a republican sense, a due dependence on the people, a due responsibility?” The Federalist No. 77, p. 507 (J. Harvard Library ed. 2009). The answer then was yes, based in part upon the President’s vulnerability to “prosecution in the common course of law.” Ibid. The answer after today is no. Never in the history of our Republic has a President had reason to believe that he would be immune from criminal prosecution if he used the trappings of his office to violate the criminal law. Moving forward, however, all former Presidents will be cloaked in such immunity. If the occupant of that office misuses official power for personal gain, the criminal law that the rest of us must abide will not provide a backstop. With fear for our democracy, I dissent. Continue Reading Here. Continue Reading Here . Here About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings. This court case retrieved on July 1, 2024, supremecourt.gov is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction. About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings. This court case retrieved on July 1, 2024, supremecourt.gov is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction. supremecourt.gov [6] The majority protests that it is “adher[ing] to time-tested practices” by “deciding what is required to dispose of this case and remanding” to lower courts to sort out the details. Ante, at 41. Yet it implicitly acknowledges that it reaches far beyond what any lower court considered or any party briefed by designating certain conduct official in the first instance. See ibid. (noting “the lack of factual analysis in the lower courts, and the lack of briefing on how to categorize the conduct alleged”). In reaching out to shield some conduct as official while refusing to recognize any conduct as unofficial, the majority engages in judicial activism, not judicial restraint.

Justice Sotomayor on Trump v United States: Today's Decision... Is Deeply Wrong

Trump v. United States Court Filing, retrieved on July 1, 2024, is part of HackerNoon’s Legal PDF Series. You can jump to any part in this filing here. This part is 11 of 21. JUSTICE SOTOMAYOR, with whom JUSTICE KAGAN and JUSTICE JACKSON join, dissenting. Today’s decision to grant former Presidents criminal immunity reshapes the institution of the Presidency. It makes a mockery of the principle, foundational to our Constitution and system of Government, that no man is above the law. Relying on little more than its own misguided wisdom about the need for “bold and unhesitating action” by the President, ante, at 3, 13, the Court gives former President Trump all the immunity he asked for and more. Because our Constitution does not shield a former President from answering for criminal and treasonous acts, I dissent. I The indictment paints a stark portrait of a President desperate to stay in power. In the weeks leading up to January 6, 2021, then President Trump allegedly “spread lies that there had been outcome-determinative fraud in the election and that he had actually won,” App. 181, Indictment ¶2, despite being “notified repeatedly” by his closest advisers “that his claims were untrue,” id., at 188, ¶11. When dozens of courts swiftly rejected these claims, Trump allegedly “pushed officials in certain states to ignore the popular vote; disenfranchise millions of voters; dismiss legitimate electors; and ultimately, cause the ascertainment of and voting by illegitimate electors” in his favor. Id., at 185–186, ¶10(a). It is alleged that he went so far as to threaten one state election official with criminal prosecution if the official did not “‘find’ 11,780 votes” Trump needed to change the election result in that state. Id., at 202, ¶31(f ). When state officials repeatedly declined to act outside their legal authority and alter their state election processes, Trump and his co-conspirators purportedly developed a plan to disrupt and displace the legitimate election certification process by organizing fraudulent slates of electors. See id., at 208–209, ¶¶53–54. As the date of the certification proceeding neared, Trump allegedly also sought to “use the power and authority of the Justice Department” to bolster his knowingly false claims of election fraud by initiating “sham election crime investigations” and sending official letters “falsely claim[ing] that the Justice Department had identified significant concerns that may have impacted the election outcome” while “falsely present[ing] the fraudulent electors as a valid alternative to the legitimate electors.” Id., at 186–187, ¶10(c). When the Department refused to do as he asked, Trump turned to the Vice President. Initially, he sought to persuade the Vice President “to use his ceremonial role at the January 6 certification proceeding to fraudulently alter the election results.” Id., at 187, ¶10(d). When persuasion failed, he purportedly “attempted to use a crowd of supporters that he had gathered in Washington, D. C., to pressure the Vice President to fraudulently alter the election results.” Id., at 221, ¶86. Speaking to that crowd on January 6, Trump “falsely claimed that, based on fraud, the Vice President could alter the outcome of the election results.” Id., at 229, ¶104(a). When this crowd then “violently attacked the Capitol and halted the proceeding,” id., at 188, ¶10(e), Trump allegedly delayed in taking any step to rein in the chaos he had unleashed. Instead, in a last desperate ploy to hold onto power, he allegedly “attempted to exploit the violence and chaos at the Capitol” by pressuring lawmakers to delay the certification of the election and ultimately declare him the winner. Id., at 233, ¶119. That is the backdrop against which this case comes to the Court. Continue Reading Here. About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings.
This court case retrieved on July 1, 2024, supremecourt.gov is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction. Trump v. United States Court Filing, retrieved on July 1, 2024, is part of HackerNoon’s Legal PDF Series. You can jump to any part in this filing here. This part is 11 of 21. Trump v. United States Court Filing, retrieved on July 1, 2024, is part of HackerNoon’s Legal PDF Series . You can jump to any part in this filing here . This part is 11 of 21. HackerNoon’s Legal PDF Series here JUSTICE SOTOMAYOR, with whom JUSTICE KAGAN and JUSTICE JACKSON join, dissenting. JUSTICE SOTOMAYOR, with whom JUSTICE KAGAN and JUSTICE JACKSON join, dissenting. Today’s decision to grant former Presidents criminal immunity reshapes the institution of the Presidency. It makes a mockery of the principle, foundational to our Constitution and system of Government, that no man is above the law. Relying on little more than its own misguided wisdom about the need for “bold and unhesitating action” by the President, ante, at 3, 13, the Court gives former President Trump all the immunity he asked for and more. Because our Constitution does not shield a former President from answering for criminal and treasonous acts, I dissent. I The indictment paints a stark portrait of a President desperate to stay in power. In the weeks leading up to January 6, 2021, then President Trump allegedly “spread lies that there had been outcome-determinative fraud in the election and that he had actually won,” App. 181, Indictment ¶2, despite being “notified repeatedly” by his closest advisers “that his claims were untrue,” id., at 188, ¶11. When dozens of courts swiftly rejected these claims, Trump allegedly “pushed officials in certain states to ignore the popular vote; disenfranchise millions of voters; dismiss legitimate electors; and ultimately, cause the ascertainment of and voting by illegitimate electors” in his favor. Id., at 185–186, ¶10(a). It is alleged that he went so far as to threaten one state election official with criminal prosecution if the official did not “‘find’ 11,780 votes” Trump needed to change the election result in that state. Id., at 202, ¶31(f ). When state officials repeatedly declined to act outside their legal authority and alter their state election processes, Trump and his co-conspirators purportedly developed a plan to disrupt and displace the legitimate election certification process by organizing fraudulent slates of electors. See id., at 208–209, ¶¶53–54. As the date of the certification proceeding neared, Trump allegedly also sought to “use the power and authority of the Justice Department” to bolster his knowingly false claims of election fraud by initiating “sham election crime investigations” and sending official letters “falsely claim[ing] that the Justice Department had identified significant concerns that may have impacted the election outcome” while “falsely present[ing] the fraudulent electors as a valid alternative to the legitimate electors.” Id., at 186–187, ¶10(c). When the Department refused to do as he asked, Trump turned to the Vice President. Initially, he sought to persuade the Vice President “to use his ceremonial role at the January 6 certification proceeding to fraudulently alter the election results.” Id., at 187, ¶10(d). When persuasion failed, he purportedly “attempted to use a crowd of supporters that he had gathered in Washington, D. C., to pressure the Vice President to fraudulently alter the election results.” Id., at 221, ¶86. Speaking to that crowd on January 6, Trump “falsely claimed that, based on fraud, the Vice President could alter the outcome of the election results.” Id., at 229, ¶104(a). When this crowd then “violently attacked the Capitol and halted the proceeding,” id., at 188, ¶10(e), Trump allegedly delayed in taking any step to rein in the chaos he had unleashed. Instead, in a last desperate ploy to hold onto power, he allegedly “attempted to exploit the violence and chaos at the Capitol” by pressuring lawmakers to delay the certification of the election and ultimately declare him the winner. Id., at 233, ¶119. That is the backdrop against which this case comes to the Court. Continue Reading Here. Continue Reading Here . Here About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings. This court case retrieved on July 1, 2024, supremecourt.gov is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction. About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings. This court case retrieved on July 1, 2024, supremecourt.gov is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction. supremecourt.gov

SLATE

slateteams.com

-- employees

Since n.d.

COMPANY RANKING

SLATE

EVERGREEN INDEX #10016

Representing this company? Click here to claim and customize this page!

Slate WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

SLATE

slateteams.com

-- employees

Since n.d.

COMPANY RANKING

SLATE

EVERGREEN INDEX #10016

RELATED COMPANIESRANK

STORIES ABOUT SLATE

Representing this company? Click here to claim and customize this page!

Slate WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!