#CoffeeScript

[hikkineetboi]

BOOP!!

@coffeescripted @xoacexo @cryos33k3r @xandermoon98 @flawed---by---design @cowsuponcows @fullcoffeedreamland @lavender1720 @zombiesama @princeofpawns @gerbatnik

[nadeshikogf]

Hiiii, I hope you're having a good day, I want to ask you how you make the color of your letters look like that?

Hallo !! I use this site !! ☆*:.｡. o(≧▽≦)o .｡.:*☆

[m0nnypie]

hiii i wanted to ask how you do the gradient on your titles, it’s really cool<33

thank you!!

HIIIIIII

well, first when I create a new post I change the text type of the post to HTML. After that, I use this site:

Then I put in the text I want, choose the colors I want and click run. Then I copy the HTML I've created and paste it into the post. Then I just switch back to rich text and that's it!

Step 1: Change the text editor to HTML (to change, just click on the post settings)

Step 2: Enter the site, enter the text you want, choose the colors and click run, then copy the generated html and paste it into the post.

Step 3: Once you've put all the text you want in gradient, switch back to rich text and you're done!

HI EVERYONE

[n4n4sblog]

how do u do that gradient thing?

Using this website, enter in your hex codes and your text! Search it up it’ll explain better than i do, but it only works on laptop <3

[eossa]

Change Post Type Indicator?

Hello, I have a question, maybe some of you have an answer / solution for it.

With the NPF posts, the default post type is always "text". In a theme, it kind of looks, well, silly if everything has a text indicator, even when the only content is an image or video.

I tried several things with CSS (tragically you cannot nest the :has() selector it seems) and consulted with ChatGPT due to my very limited knowledge of JavaScript. The result is something like in the JS Fiddle below.

While the code works in the JS Fiddle, it does not work in my theme, as can be seen in the example post below:

Thank you in advance for any suggestions, help, solutions to make this thing work! <3

Solved thanks to the amazing @lushwave !!

[swansdiary]

How you do the color thing on your posts??? Its so pretty! 😍

thank u so much! i used this website to do the colour gradient text -

and i found this tutorial that explains in detail how to use it-

i hope it helps <3

[hedgehoghavoc]

@cxffeeshxp said: How the hell you mix the text color

[thatenbypan]

DIDNT WORK TRY AGAIN.

- ANGRY colored text anon.

LOOK!!!!!!!!!!!!! also put text editor to html

[minkkumaz]

hii omi! i just wanted to ask how you get so much color options in your works?? because i only get the 'basic neon' ones if you get what im talking about

hi sunni! so im not sure what device you use, and honestly i have no clue how to do any of it on mobile. bc if u didnt know i do all of my work on pc ^_^ im a little gamer when im not doing my 9 to 5 on tumblr LOLL

but anyways if you are on computer i used this tutorial!

https://youtu.be/Yf6ZnhnSgLc

basically in the tut you go to this website https://jsfiddle.net/j7vLfbw1/22/

when you are there, put your text into the first box then pick the colors. afterward, click the 'run' button. copy the text that shows up in the second box.

afterward, go to your tumblr post and click on the gear in the corner. where it says 'text editor' click on 'rich text' and change to html mode. then u can just paste the text and preview it to make sure it looks good ^_^

[jameszhall]

Developers Beware: 6 Languages That May Be Obsolete by 2026.

Let’s talk truth for a second.

As developers, we fall in love with tools. We defend our favorite languages like they’re our hometown football team. But in tech?

Loyalty doesn’t keep you employed. Relevance does.

Languages rise. Languages fall. And if you're still building your future on a language that's fading out… you might be coding yourself into a corner.

Here are 6 programming languages that may be gone (or nearly irrelevant) by 2026 — and the smarter alternatives that’ll keep your skills sharp, your job safe, and your work future-proof.

💀 1. Perl "The scripting legend nobody invites to the party anymore."

Perl was once the web’s Swiss Army knife. Today? It's mostly a maintenance nightmare.

Syntax so cryptic it looks like line noise

Lost the scripting throne to Python years ago

Hiring demand? Flatlining

👨‍🔧 Still using it? You’re likely holding together legacy glue code that someone forgot existed.

💡 Switch to: ✔️ Python for clean, powerful scripting ✔️ Bash for sysadmin tasks ✔️ Go for better performance

🧟 2. Objective-C "Used to be Apple's favorite. Now it's Swift’s tired uncle."

There’s no shade here — Objective-C had a solid run. But Apple has clearly moved on.

Swift is faster, cleaner, and loved by new devs

Apple’s docs and frameworks scream “Swift only”

Most new iOS projects don’t even touch Objective-C anymore

💡 Switch to: ✔️ Swift if you're in Apple’s ecosystem ✔️ Kotlin if you’re doing Android or cross-platform mobile

Future devs won’t learn Objective-C. They’ll just debug it until it dies.

🪫 3. VB "Corporate. Clunky. Quietly disappearing."

You’ll still find it buried in legacy enterprise apps — but that’s about it.

Microsoft is putting its weight behind C# and NET Core

Minimal innovation

Not really “modern dev” friendly

💡 Switch to: ✔️ C# for modern NET work ✔️ TypeScript if you want flexibility ✔️ Python if you want clarity

If your job depends on VB.NET, it may be time to ask: What’s next?

🧠 4. Lisp (and Scheme) "Brilliant… but basically a museum exhibit."

Lisp is historically iconic. And… practically forgotten in most modern dev stacks.

Great for learning recursion and theory

Bad for landing a dev job in 2025

Minimal real-world demand

💡 Switch to: ✔️ Python for data & AI ✔️ Rust for systems-level brilliance ✔️ Elixir if you love functional programming

Lisp will always be respected. But respected isn’t hired.

🪦 5. Haskell "Beautiful, complex, and unfortunately… unused."

Dev Twitter loves it. Real-world hiring managers? Not so much.

Pure functional — which = steep learning curve

Poor ecosystem for production apps

Mostly used in academia or niche startups

💡 Switch to: ✔️ Elixir if you want practical functional code ✔️ Rust or TypeScript for safer, modern development

Learning Haskell will make you smarter. But sadly, not busier.

☕ 6. CoffeeScript "What if JavaScript… but slightly weirder?"

CoffeeScript once made JS tolerable. Then ES6+ and TypeScript showed up and made it… pointless.

No longer solves a real problem

Shrinking community

Most teams have already migrated

💡 Switch to: ✔️ TypeScript — all the benefits, none of the baggage ✔️ Modern JS (ES2020+) — lean, powerful, and everywhere

Unless you’re maintaining old code, CoffeeScript is a ghost from the past.

🚨 Quick Survival Map: What to Leave & What to Learn 🛑 Fading ✅ Learn Instead Perl Python, Go Objective-C Swift, Kotlin VB,C#, TypeScript, Python Lisp/Scheme Python, Rust, Elixir Haskell Elixir, Rust, TypeScript CoffeeScript TypeScript, ES6+ JS

🧠 Final Thought: Learn What Lasts You don’t have to chase every shiny framework or hop languages every six months.

But if you're spending your precious time mastering a tool the world’s moving on from…

You’re not future-proofing. You’re future-dodging.

Instead:

Learn what’s growing.

Master what companies actually use.

Focus on writing better code — not just clever code.

The tools don’t define your talent. But they do define your opportunities.

[kitchenswhispers]

Healthy Smoothie Bowl for Breakfast171# hello-world Just another repository Hi Humans! Hubot here, I like Node.js and Coffeescript (that's what I'm made of!). I've had tacos on the moon and find them far superior to Earth tacos.

[marlog-5]

testing testing one two threee

testing testing one two three

Heeeyyy it's ya boy... uh... skinny penis

[fromdevcom]

Chatter is an enterprise social network and collaboration environment. Force.com exposes various useful information from Chatter such as users, organizations, groups, feed-items through APIs. Using this information, we can build a proof-of-concept dashboard which will show a user’s or organization’s feed in real-time. Real-time dashboard can provide an accurate understanding of what is happening in an organization. This tutorial expects that you are an intermediate-level web application developer and have a few weeks of experience with Rails and related ecology. This means you should be familiar with building blocks of a Rails app and terms like OAuth, REST, Callback, bundler, gem etc. Here is an outline of how things will work: User can login to our Rails4 powered dashboard (a connected app) using ‘Sign in with Salesforce’ (Oauth 2). We use OAuth to get a secret token for each user from salesforce.com. We can use the token to call APIs. Our goal is to receive a callback to server whenever anything is posted on Chatter. Unfortunately, Force.com doesn’t support a PushTopic for FeedItem, so we will use a work-around to trigger a callback whenever a FeedItem is created. First, we will create a trigger on FeedItem, this trigger will create a custom object named ProxyFeedItem, which will copy necessary fields like body, time, parent_id etc. from the FeedItem. Using a faye client embedded in restforce client, we will listen to a PushTopic for ProxyFeedItem. ProxyFeedItem will be created whenever there’s an update to any FeedItem. This will send a callback to the server with data of the ProxyFeedItem. We will need to forward this incoming data to user’s browser. We will set up another faye channel and just transfer the data we received in step 4. First, go to https://developer.salesforce.com/signup and register for your free Developer Edition (DE) account. For the purposes of this example, I recommend sign up for a Developer Edition even if you already have an account. This ensures you get a clean environment with the latest features enabled. After sign up, make a connected app by following the directions found in this article from the salesforce.com developer portal. Use http://localhost:3000 as Start URL, enable Oauth settings, select appropriate permissions and use http://localhost:3000/oauth/salesforce/callback as callback URL. When you create your app, you will get the app’s Consumer Key and Consumer Secret. We have set up everything that we need from Force.com for this section and we can move on to our web application code. Create a new Rails4 application with rails new chatter-dashboard This will go ahead and create a Rails4 project with the name ‘chatter-dashboard’ and install the dependencies mentioned in Gemfile. Actually, we need a few more dependencies. Change Gemfile to the following: source 'https://rubygems.org' # Bundle edge Rails instead: gem 'rails', github: 'rails/rails' gem 'rails', '4.1.0' # Use sqlite3 as the database for Active Record gem 'sqlite3' # Use SCSS for stylesheets gem 'sass-rails', '~> 4.0.3' # Use Uglifier as compressor for JavaScript assets gem 'uglifier', '>= 1.3.0' # Use CoffeeScript for .js.coffee assets and views gem 'coffee-rails', '~> 4.0.0' # See https://github.com/sstephenson/execjs#readme for more supported runtimes # gem 'therubyracer', platforms: :ruby # Use jquery as the JavaScript library gem 'jquery-rails' # Turbolinks makes following links in your web application faster. Read more: https://github.com/rails/turbolinks gem 'turbolinks' # Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder gem 'jbuilder', '~> 2.0' # bundle exec rake doc:rails generates the API under doc/api. gem 'sdoc', '~> 0.4.0', group: :doc # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring gem 'spring', group: :development # Use ActiveModel has_secure_password # gem 'bcrypt', '~> 3.1.7'

# Use unicorn as the app server # gem 'unicorn' # Use Capistrano for deployment # gem 'capistrano-rails', group: :development # Use debugger # gem 'debugger', group: [:development, :test] # Using customized version to fix issue #103 in restforce gem 'restforce', :git => 'git@github.com:malavbhavsar/restforce.git', :branch => 'patch-1' # Use omniauth for handlling OAuth with Salesforce gem 'omniauth' # Add omniauth policy for saleforce gem 'omniauth-salesforce' # Print pretty gem 'awesome_print' # Development only gems group :development do gem 'better_errors' gem 'binding_of_caller' end # Add faye for pub/sub, using customized version to avoid problems from # issue 263 and other related issue gem 'faye', :git => 'git@github.com:faye/faye.git' # private_pub to easily do pub-sub with browser, using customized version # to make sure that we get faye.js which is not packed when using faye gem # from master gem 'private_pub', :git => 'git@github.com:malavbhavsar/private_pub.git' # Puma for our main server concurrently gem 'puma' # Thin for running faye server gem 'thin' Run bundle install, which will install additional dependencies. To start our server, run rails s puma; this will run rails with a puma server and you should be able to see a welcome page on http://localhost:3000. The next step is to set up Oauth with salesforce.com. Add Consumer Key and Consumer Secret to chatter-dashboard/config/secrets.yml development: secret_key_base: salesforce_key: salesforce_secret: test: secret_key_base: # Do not keep production secrets in the repository, # instead read values from the environment. production: secret_key_base: Create a chatter-dashboard/config/initializers/omniauth.rb file and add the following code into it: Rails.application.config.middleware.use OmniAuth::Builder do provider :salesforce, Rails.application.secrets.salesforce_key, Rails.application.secrets.salesforce_secret , :scope => "id api refresh_token" end This configures our omniauth and omniauth-salesforce gems. It has basically added a middleware in our Rails application, which will handle Oauth for us. You can read the documentation for these gems to dig deeper. Now, run the following commands to set up two controllers and relevant routes; one for the login page and the other for the feed page: rails g controller Login login rails g controller Feed feed Now, in the chatter-dashboard/config/routes.rb file, add the following routes: get '/auth/:provider/callback', to: 'sessions#create' root to: 'login#login' This will basically add a callback route to which the user will be redirected to by Force.com after the Oauth procedure has finished successfully. We have also added a root route, so that whenever we go to http://localhost:3000, it will trigger the login#login route. Currently, it’s just an empty page. Let’s add a ‘Sign in with Salesforce’ link to it. Add the following line to chatter-dashboard/app/views/login/login.html.erb: If you hit refresh and click on ‘Sign in with Salesforce’, you will be taken to the login page of salesforce.com if you are not signed in. After signing in and giving the app permissions, you will be redirected to http://localhost:3000/auth/salesforce/callback, but we haven’t implemented matching sessions#create yet. Let’s do that by doing rails g controller Sessions create. For the implementing create method, use the following code: class SessionsController < ApplicationController def create set_client ap @client redirect_to '/feed/feed' end protected def auth_hash_credentials request.env['omniauth.auth'][:credentials] end def set_client @client = Restforce.new :oauth_token => auth_hash_credentials[:token], :refresh_token => auth_hash_credentials[:refresh_token], :instance_url => auth_hash_credentials[:instance_url], :client_id => Rails.application.secrets.salesforce_key, :client_secret => Rails.application.secrets.salesforce_secret end end Here, we parse the callback request coming from Force.

com and get oauth_token, refresh_token etc and create a restforce client. If you see something like the following in your console, then you have completed the first section of this tutorial: In the first section of the tutorial, we set up Oauth with salesforce.com and created a restforce client object. In this section, we want Force.com to notify us of any changes in the FeedItem object of Chatter. Unfortunately, Salesforce streaming API doesn’t support FeedItem yet, so we will have to do a work-around. Create a custom object named ProxyFeedItem. Add necessary fields like Body, Type, CommentCount, LikeCount, CreatedById from FeedItem Now, let’s setup a trigger on FeedItem. You can do this by going to ‘Setup’ on your Force.com and search for ‘FeedItem Trigger’. Use the following code: trigger FeedItemListen on FeedItem (after insert, after update) for(FeedItem f : Trigger.new) ProxyFeedItem__c p = new ProxyFeedItem__c(Body__c = f.Body, CommentCount__c = f.CommentCount, LikeCount__c = f.LikeCount, Type__c = f.Type, User__c = f.CreatedById); insert p; Whenever this is triggered, we get the data from Trigger.new iterate over it and create our custom object ProxyFeedItem for each FeedItem in the data. Now, we have to create a PushTopic, which will listen to any changes in all ProxyFeedItem (and in turn FeedItem) We will subscribe to this PushTopic and send the changes to browser. Following the streaming example given in the restforce docs, we can create a file at chatter-dashboard/lib/chatter_listen.rb like the following: module ChatterListenEM def self.start(client) pushtopics = client.query('select Name from PushTopic').map(&:Name) unless pushtopics.include?('AllProxyFeedItem') client.create! 'PushTopic', ApiVersion: '30.0', Name: 'AllProxyFeedItem', Description: 'All ProxyFeedItem', NotifyForOperations: 'All', NotifyForFields: 'All', Query: "SELECT Id, Body__c, CommentCount__c, LikeCount__c, Type__c, User__c from ProxyFeedItem__c" end Thread.abort_on_exception = true Thread.new EM.run do client.subscribe 'AllProxyFeedItem' do die_gracefully_on_signal end def self.die_gracefully_on_signal Signal.trap("INT") EM.stop Signal.trap("TERM") EM.stop end end Whenever ChatterListenEM.start is called, it creates a PushTopic named ChatterFeedItem, if it doesn’t already exist. Next, it creates a new thread and subscribes to that PushTopic in it. Whenever we receive a message, we pass it a Faye channel e.g. messages/new using private_pub. private_pub is a ruby gem, which makes it easier to setup a pub-sub type mechanism between a web server and browser. You can learn more about it in this screencast on private pub Before going to private_pub and related stuff, let’s call our ChatterListenEM.start method from SessionController. There is just one minor change: require 'chatter_listen' class SessionsController < ApplicationController def create set_client ChatterListenEM.start(@client) redirect_to '/feed/feed' end protected def auth_hash_credentials request.env['omniauth.auth'][:credentials] end def set_client @client = Restforce.new :oauth_token => auth_hash_credentials[:token], :refresh_token => auth_hash_credentials[:refresh_token], :instance_url => auth_hash_credentials[:instance_url], :client_id => Rails.application.secrets.salesforce_key, :client_secret => Rails.application.secrets.salesforce_secret end end Now, let’s set up private_pub. Run rails g private_pub:install on console. It will create and place necessary files like private_pub.ru, private_pub.yml and faye.js, private_pub.js in asset-pipeline. To make rails aware of faye.js and private_pub.js files, add them to the chatter-dashboard/app/assets/javascripts/application.js file. // This is a manifest file that'll be compiled into application.js, which will include all the files // listed below. // // Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts, // or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.

// // It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the // compiled file. // // Read Sprockets README (https://github.com/sstephenson/sprockets#sprockets-directives) for details // about supported directives. // //= require jquery //= require jquery_ujs //= require faye //= require private_pub //= require turbolinks //= require_tree . Start our Faye server in a different console. This will handle pub-sub for us. rackup private_pub.ru -s thin -E production All that is left to do now is to subscribe to the channel /messages/new and print our data. We can take easy examples from the private_pub documentation and add the following to our chatter-dashboard/app/views/feed/feed.html.erb: and the following to our chatter-dashboard/assets/javascripts/feed.js: PrivatePub.subscribe("/messages/new", function(data, channel) console.log(data.chat_message); ); Now, go to http://localhost:3000, ‘Login with Salesforce’ and you will end up on the feed page. Open the developer console and in another tab open the Chatter tab of salesforce.com. If you do a text post, you will be able to see a real time update in the console. Here’s a proof of concept, showing the dashboard in action: We just implemented a system like below: Instead of printing data in console, you can easily feed it into any frontend framework like angular, ember etc. and create a great real-time dashboard. We also have left out few things in this proof-of-concept prototype e.g. we have to secure our faye channels. One way of doing this is creating a different channel for each user. e.g. /messages/new/user_id and subscribe the user only to that particular channel. Additionally, use SSL. If you are handling any real user data, it is important that you secure the data being transferred. Force.com makes sure to secure the data and only provides developers with data over SSL using OAuth. It is however the responsibility of the developer to ensure secure communication in any RESTful app. For more information, you should refer to Security Resources. You can find the code for this project at github chatter-dashboard Resources For a comprehensive set or resources, check out: About The Author: This article is created by Malav Bhavsar. Please feel free to ask questions in the comment section, open issues in the github repository or contact me at malav.bhavsar@gmail.com