Skip to main content

GO lang to print colored output 

package main

import (
	"fmt"
)

func Red(format string, args ...interface{}) {
	fmt.Printf("\033[31m"+format+"\033[0m", args...)
}

func Green(format string, args ...interface{}) {
	fmt.Printf("\033[32m"+format+"\033[0m", args...)
}

func Yellow(format string, args ...interface{}) {
	fmt.Printf("\033[33m"+format+"\033[0m", args...)
}

func Blue(format string, args ...interface{}) {
	fmt.Printf("\033[34m"+format+"\033[0m", args...)
}

func Magenta(format string, args ...interface{}) {
	fmt.Printf("\033[35m"+format+"\033[0m", args...)
}

func Cyan(format string, args ...interface{}) {
	fmt.Printf("\033[36m"+format+"\033[0m", args...)
}

func main() {
	// Set the foreground color to red
	Red("Hello, world!\n")
	Yellow("Hello, world!\n")
	Green("Hello, world!\n")
	Magenta("Hello, world!\n")
	Cyan("Hello, world!\n")
	Blue("Hello, world!\n")

}
<
Previous Post
Installing golang compiler in linux machine
>
Blog Archive
Archive of all previous blog posts

Comments

Post a Comment

Popular posts from this blog

Boosting Golang Application Performance with Query Result Caching

In the realm of Golang application development, optimizing database queries is a critical aspect of ensuring smooth and efficient user experiences. One powerful technique to achieve this is Query Result Caching . In this blog post, we will delve into query result caching strategies, focusing on caching frequently executed queries in an in-memory cache (using Redis as an example). You'll learn how to reduce database load and improve response times, all while enhancing your Golang application's performance. The Power of Query Result Caching Consider a scenario where your Golang application frequently fetches data from a database. Without caching, every request to retrieve the same data results in a database query, even if the data hasn't changed since the last request. This can be resource-intensive and lead to slower response times. Query result caching is the practice of storing the results of frequently executed queries in an in-memory cache, such as Redis or Memcached....
Read more

Enhancing Database Security and Performance with Parameterized Queries

In the world of database programming, security and performance are paramount concerns. One technique that addresses both of these concerns is the use of parameterized queries or prepared statements. In this blog post, we'll explore the significance of parameterized queries, their role in preventing SQL injection, and how they can potentially improve query execution speed. We'll provide practical examples to illustrate the power and versatility of this essential query optimization technique. The Importance of Parameterized Queries Parameterized queries , also known as prepared statements , are a mechanism in which placeholders are used for data values in SQL queries. These placeholders are later bound to actual data values when the query is executed. Parameterized queries offer several crucial advantages: Protection Against SQL Injection: One of the primary benefits of parameterized queries is their ability to prevent SQL injection attacks. By separating SQL cod...
Read more

Profiling CPU Usage in Go: Boosting Performance

Image
Profiling CPU Usage in Go Programs Profiling CPU usage in Go allows you to measure the time your program spends executing various functions and code paths. This insight is invaluable for optimizing your code. Go provides built-in tools to help you with this. To get started with CPU profiling, you'll need to: Import the net/http/pprof Package : This package exposes the profiling functionality via HTTP endpoints. Include it in your code like this: import _ "net/http/pprof" Start an HTTP Server : You'll want to start an HTTP server that serves profiling data. go func() { log.Println(http.ListenAndServe("localhost:6060", nil)) }() Instrument Your Code : Use the runtime/pprof package to start and stop CPU profiling within your application: import ( "net/http" _ "net/http/pprof" "os" "runtime/pprof" ) func main() { go func() { log.Println(http.Lis...
Read more